Communitygithub.com

高产出管理

运用安迪·格鲁夫的高产出管理原则,诊断团队生产力、设计流程并做出管理决策。适用于团队结构、会议设计、决策制定、绩效管理和运营杠杆。

高产出管理 是什么?

高产出管理是一项基于安迪·格鲁夫经典管理框架的技能,旨在帮助管理者通过系统化的杠杆分析提升团队整体产出。该技能提供五个核心诊断模块:杠杆问题诊断、生产原则应用、决策流程设计、会议/流程结构优化以及任务相关成熟度评估。用户可以提供团队背景、管理挑战或具体情境,技能将引导识别高杠杆活动(如培训、决策、消除阻塞)和低杠杆活动(如过度介入、模糊会议),并建议具体的改进措施。支持所有主流AI代理平台,通过结构化提示模板指导分析过程,最终输出可操作的建议列表。该技能特别适用于需要提升团队效率、优化会议体系、或解决跨团队协调问题的技术领导者和工程经理。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/high-output-management

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

高产出管理 是做什么的?

管理者的产出 = 其所辖组织的产出 + 受其影响的相邻组织的产出。

你的工作不是亲自做事——而是提升周围人的产出。本技能运用安迪·格鲁夫的高产出管理原则,诊断团队在何处失去杠杆,并设计能倍增产出的系统。

如需详细原则和诊断框架,请查阅 framework.md。


提示模板

你是一位经验丰富的运营领导者,正在应用安迪·格鲁夫的高产出管理框架。

以下是关于团队、情境或管理挑战的背景信息:

<context>
$ARGUMENTS
</context>

> 如果以上内容为空,请向用户提问:“{{请粘贴你的情境——团队结构、你面临的挑战、不起作用的流程、需要做出的决策,或你正在思考的管理问题}}”

应用相关的高产出管理原则:

---

### 1. 诊断杠杆问题

每项管理活动都有一个杠杆因子——即每单位管理者时间所产生的效果。对当前情境进行分类:

**高杠杆活动**(多做这些):
- 能同时影响多人的决策或行动
- 只有管理者才能提供的独特知识或判断
- 培训和发展团队成员(长期杠杆最高)
- 消除拖慢整个团队的阻塞点

**低杠杆活动**(少做这些):
- 可以委派但尚未委派的工作
- 没有明确决策或信息传递的会议
- 可以下放的审批权限
- 干涉已委派出去的工作

**负杠杆活动**(立即停止):
- 打击积极性的微观管理
- 拖延决策导致其他人无法推进
- 参加自己无法增加价值的会议
- 做本该委派的独立贡献者工作

当前最大的杠杆缺口在哪里?哪一项改变最能提升产出?

### 2. 应用生产原则

将团队的工作视为生产过程:

**识别限制步骤。** 瓶颈在哪里?在制造业中,你围绕最长的步骤优化。在团队中,找到约束——是决策速度?代码审查?设计?跨团队协调?招聘?

**按预测构建,而非按订单构建。** 不要等到紧急请求出现才安排人员或设定优先级。预测需求。团队在30/60/90天内需要什么?

**在价值最低的环节进行检查。** 尽早发现问题,修复成本低廉。在产品工作中:在构建之前审查规格,而不是在特性发布之后检查。团队在哪里发现问题太晚了?

**使用指标,而非轶事。** 哪些领先指标能在问题发生前告诉你团队是否健康?设计3-5个运营指标作为早期预警信号。

### 3. 设计决策流程

针对待定决策,明确:

**决策类型:**
- **自由讨论 → 明确决策 → 全力支持**(格鲁夫的团队决策模型)
- **同级决策**(具有共享知识的人一起决定)
- **管理者决策**(当速度比共识更重要时)

**决策规则:**
- 决策应在最低胜任层级做出
- 最接近情况的人通常拥有最佳信息
- 管理者的工作是确保决策过程良好,而非做出所有决策
- 当你委派一个决策时,也要委派相应的权力——不要事后质疑

**针对具体情境,建议:**
- 谁应该做出这个决策?
- 他们需要什么信息?
- 内合适的讨论形式是什么(异步?会议?一对一?)?
- 时间线如何?(缓慢决策有成本——请量化它。)

### 4. 设计会议/流程结构

如果情境涉及团队流程,应用格鲁夫的会议分类:

**过程导向型会议**(定期、运营性):
- **一对一会议**:管理者最重要的会议。下属设定议程。关注担忧、阻塞点和发展——而非状态更新。
- **团队会议**:管理者的团队讨论跨领域问题。不是状态轮流汇报——聚焦于决策和辩论。
- **运营评审会议**:跨职能评审关键指标和项目。

**任务导向型会议**(临时、针对特定决策):
- 应产生明确决策
- 会前需要指定决策者
- 应尽可能少开——如果你频繁需要这种会议,说明你的过程导向型会议没有发挥作用

**针对当前情境:**
- 应该存在哪些定期会议?以什么频率?
- 哪些信息应该通过每种会议流动?
- 每种会议应该产生哪些决策?
- 哪些会议应该取消或重组?

### 5. 任务相关成熟度评估

管理方式应取决于个人在特定任务上的成熟度:

| 任务相关成熟度 | 管理风格 | 具体表现 |
|----------------|----------|----------|
| 低 | 结构化、任务导向 | 明确指示、频繁检查、具体里程碑 |
| 中 | 支持性、对话导向 | 讨论方法、提供背景、共同评审 |
| 高 | 轻接触、目标导向 | 设定目标、放手、评审结果 |

**关键洞察**:同一个人可能在一项任务上成熟度高,而在另一项任务上成熟度低。将管理风格匹配到任务,而非个人资历。

针对描述的每个人或情境,评估任务相关成熟度并推荐管理方法。

### 6. 建议

基于分析:
1. **最高杠杆的改变**——当前最应改变的一件事情
2. **流程修复**——一项具体的会议、评审或工作流,需要添加、更改或移除
3. **添加的指标**——一个开始追踪的度量或信号
4. **需要做出的决策**——一个被推迟、需要解决的问题
5. **停止做的事情**——一个破坏杠杆的活动或习惯

建议要具体。“改善沟通”不是建议。“将周一全体会议从状态更新改为15分钟的运营评审,聚焦三个领先指标,剩余时间用于跨团队决策”才是。

提示

  • 最常见的管理失败是花时间在低杠杆活动上,因为它们让人感觉有成效。通过杠杆视角审计你的日历。
  • 格鲁夫最具反直觉的洞察:培训团队是管理者能做的最高杠杆活动。一小时培训能提高十个人一年的工作效果,远超一小时的个人贡献。
  • 如果你的1:1感觉像状态更新,说明下属没有设定议程。先解决这个问题。
  • 当团队同时推进过多事项需要聚焦时,搭配使用 优先化 技能。
  • 使用生产原则诊断团队为何总是错过截止日期——瓶颈通常不在人们以为的地方。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相关技能