菜单
An organizational model where a single leader is fully accountable for a specific goal and controls all cross-functional resources needed, minimizing external dependencies. Amazon's alternative to matrixed organizations.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Coowoolf/insighthunt-skills --skill single-threaded-leadership-model命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is critical.
Use when designing AI agents or chatbots, when raw model outputs feel like a black box, or when building natural language interfaces that need structure and trust
基于 SOC 职业分类
正在显示 SKILL.md
| name | Single-Threaded Leadership Model |
| description | An organizational model where a single leader is fully accountable for a specific goal and controls all cross-functional resources needed, minimizing external dependencies. Amazon's alternative to matrixed organizations. |
"The best way to fail at inventing something is to make it somebody's part-time job." — Bill Carr
An organizational model where a single leader is fully accountable for a specific business goal and controls the cross-functional resources (engineering, product, marketing) needed to achieve it, minimizing external dependencies.
PROJECT ORIENTATION (Matrixed) SINGLE-THREADED (Program)
┌────────────────────────────┐ ┌────────────────────────────┐
│ Resources swarmed to │ │ Dedicated cross-functional │
│ temporary projects │ │ teams │
├────────────────────────────┤ ├────────────────────────────┤
│ High dependency on │ │ Control of own resources │
│ central teams │ │ and roadmap │
├────────────────────────────┤ ├────────────────────────────┤
│ Leaders referee every │ │ Leaders referee resource │
│ roadmap item │ │ allocation only │
├────────────────────────────┤ ├────────────────────────────┤
│ Diluted ownership │ │ Clear single-owner │
│ │ │ accountability │
└────────────────────────────┘ └────────────────────────────┘
Long-term ownership beats temporary task forces.
Teams that own their resources move faster.
Reduce "coordination tax" by decoupling architectures.
Roadmap, resources, and results under one person.
STEP 1: Identify Strategic Goal
└── What outcome needs dedicated ownership?
└── What's currently "everyone's job" (nobody's job)?
STEP 2: Appoint Single-Threaded Leader
└── One person, fully dedicated
└── Cannot be their "part-time job"
STEP 3: Assign Cross-Functional Resources
└── Give them their own engineers
└── Give them their own designers/PMs
STEP 4: Decouple Architecture
└── APIs instead of shared code
└── Minimize dependencies on central teams
STEP 5: Implement Countermeasures
└── Bar Raisers to maintain quality
└── Functional guilds for skill development
❌ Creating single-threaded teams without decoupling architecture first
❌ Failing to implement countermeasures (like Bar Raisers)
❌ Making it someone's part-time job
Prime Video organized into separate single-threaded teams for TV apps, game consoles, and mobile phones, each with their own resources and roadmaps.
Source: Bill Carr, Co-author of "Working Backwards", Lenny's Podcast