Back to Details

delegating-work

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Delegating Work

工作授权

Scope

适用范围

Covers
  • Delegating a specific project/problem/decision to a direct report (or cross-functional owner)
  • Transferring context without control (clear outcomes + guardrails, not step-by-step instructions)
  • Setting decision rights, check-in cadence, and “in-the-details” quality reviews without micromanaging
When to use
  • “Help me delegate this project/task to someone on my team.”
  • “I’m holding onto too much / I need to give away my Lego.”
  • “I’m worried I’m micromanaging—how do I stay in the details but empower ownership?”
  • “Draft a delegation brief + decision rights + check-in plan.”
When NOT to use
  • The work is primarily a performance problem (use coaching/feedback workflows instead)
  • You need to decide what work to do (prioritization/scope first)
  • You lack a clear outcome, constraints, or success criteria (do a quick problem-definition first)
适用场景
  • 将特定项目/问题/决策授权给直属下属（或跨职能负责人）
  • 传递上下文而非控制权（明确成果+边界规则，而非分步指令）
  • 在不进行微观管理的前提下，设定决策权限、沟通跟进节奏和“细节层面”的质量评审
适用时机
  • “帮我把这个项目/任务授权给团队里的某个人。”
  • “我手上管的事情太多了 / 我需要放权。”
  • “我担心自己在微观管理——如何在把控细节的同时赋能下属自主负责？”
  • “起草一份授权简报+决策权限+沟通跟进计划。”
不适用时机
  • 工作问题主要是绩效问题（此时应采用辅导/反馈流程）
  • 你还未确定要做哪些工作（需先完成优先级排序/范围定义）
  • 你缺乏明确的成果目标、约束条件或成功标准（需先完成快速的问题定义）

Inputs

输入信息

Minimum required
  • The work item to delegate (project/problem/decision) + why now
  • Desired outcome (definition of done) + success metrics or acceptance criteria
  • Constraints/non-negotiables (timeline, budget, quality bar, policies, stakeholders)
  • Delegatee context (role, current load, experience level, growth goals if relevant)
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If details are unavailable, proceed with explicit assumptions and label unknowns.
必备输入信息
  • 待授权的工作项（项目/问题/决策）+ 为何选择此时授权
  • 预期成果（完成定义）+ 成功指标或验收标准
  • 约束条件/不可协商项（时间线、预算、质量标准、政策、相关利益方）
  • 被授权人信息（岗位、当前工作量、经验水平、相关成长目标）
缺失信息处理策略
  • 从references/INTAKE.md中最多提出5个问题。
  • 若无法获取细节，则基于明确假设推进，并标注未知信息。

Outputs (deliverables)

输出成果（交付物）

Produce a Delegation Pack (Markdown in-chat, or files if requested) in this order:
  1. Delegation brief (outcome, context, constraints, stakeholders, timeline)
  2. Decision rights + guardrails (what they can decide, escalation triggers, review points)
  3. Context handoff pack (links, background, “known gotchas”, example outputs)
  4. Execution cadence (check-ins, update format, what “good” looks like)
  5. Review plan (how to be in the details without telling them how to do it)
  6. Debrief plan (learning capture + ownership updates)
  7. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
生成一份Delegation Pack（支持聊天内Markdown格式，或按需生成文件），内容顺序如下：
  1. 授权简报（成果目标、背景上下文、约束条件、利益相关方、时间线）
  2. 决策权限与边界规则（被授权人可自主决策的事项、升级上报触发条件、评审节点）
  3. 上下文移交包（相关链接、背景信息、“已知陷阱”、示例输出）
  4. 执行跟进节奏（沟通频次、更新格式、“合格成果”定义）
  5. 评审计划（如何在不干预执行细节的前提下把控质量）
  6. 复盘计划（经验总结+所有权更新）
  7. 风险/待解决问题/下一步行动（必须包含）
模板参考：references/TEMPLATES.md

Workflow (8 steps)

工作流程（8个步骤）

1) Frame the delegation decision

1) 明确授权决策

  • Inputs: Work item + why now; constraints.
  • Actions: Define the outcome, the “why” (business context), and what must not change (non-negotiables). Decide what “good” looks like.
  • Outputs: Draft Delegation Brief (top section).
  • Checks: The outcome is measurable/testable (someone can say “done” unambiguously).
  • 输入信息：待授权工作项+授权时机；约束条件。
  • 行动：定义成果目标、“原因”（业务背景）以及不可变更的规则（不可协商项）。明确“合格成果”的标准。
  • 输出：授权简报草稿（核心部分）。
  • 校验：成果目标需可衡量/可验证（能够明确判断“已完成”）。

2) Pick the owner + choose the autonomy level

2) 选定被授权人并确定自主权限等级

  • Inputs: Candidate owner(s); their experience and growth goals.
  • Actions: Select the delegatee. Set an explicit autonomy level (e.g., “propose + I approve” vs “you decide, inform me”). Call out which parts are “on assignment” vs “high flexibility.”
  • Outputs: Owner + autonomy statement + boundaries.
  • Checks: Both of you can repeat: “What decisions are yours vs mine?”
  • 输入信息：候选被授权人；其经验水平与成长目标。
  • 行动：选定被授权人。明确自主权限等级（例如：“提出方案+我审批” vs “你自主决策，事后告知我”）。区分哪些部分是“指定任务” vs “高度灵活”。
  • 输出：被授权人+权限说明+边界规则。
  • 校验：双方能够清晰复述：“哪些决策由你负责，哪些由我负责？”

3) Transfer context (not instructions)

3) 移交上下文（而非执行指令）

  • Inputs: Background docs; prior decisions; stakeholders; constraints.
  • Actions: Provide full context so the owner can connect the dots. Share the “why”, the tradeoffs, and known pitfalls. Avoid prescribing the exact path.
  • Outputs: Context Handoff Pack.
  • Checks: Owner can explain the problem, constraints, and success criteria in their own words.
  • 输入信息：背景文档；过往决策；利益相关方；约束条件。
  • 行动：提供完整上下文，帮助被授权人理清关联逻辑。分享“原因”、权衡因素以及已知陷阱。避免指定具体执行路径。
  • 输出：上下文移交包。
  • 校验：被授权人能够用自己的话解释问题、约束条件和成功标准。

4) Define decision rights + guardrails

4) 定义决策权限与边界规则

  • Inputs: Non-negotiables; risks; stakeholders.
  • Actions: Write decision rights, escalation triggers, and review points. Set “red lines” (quality, policy, safety, customer impact).
  • Outputs: Decision Rights + Guardrails.
  • Checks: Escalation triggers are specific (not “if it feels risky”).
  • 输入信息：不可协商项；风险；利益相关方。
  • 行动：明确决策权限、升级上报触发条件和评审节点。设定“红线”（质量、政策、安全、客户影响）。
  • 输出：决策权限与边界规则。
  • 校验：升级上报触发条件需具体明确（而非“感觉有风险时”）。

5) Align on plan + milestones (owner-led)

5) 对齐计划与里程碑（由被授权人主导）

  • Inputs: Draft Delegation Brief + guardrails.
  • Actions: Ask the owner to propose a plan, milestones, and tradeoffs. Act as a thought partner: ask questions instead of giving the answer.
  • Outputs: Milestone plan + first-week plan.
  • Checks: Plan has milestones tied to outcomes, not just activities.
  • 输入信息：授权简报草稿+边界规则。
  • 行动：要求被授权人提出计划、里程碑和权衡方案。作为思路伙伴：多提问而非直接给出答案。
  • 输出：里程碑计划+第一周执行计划。
  • 校验：计划中的里程碑需与成果目标绑定，而非仅罗列活动。

6) Set the execution cadence

6) 设定执行跟进节奏

  • Inputs: Timeline; team routines; stakeholder needs.
  • Actions: Set check-in frequency, update format, and what you want to see (risks, decisions, asks). Establish how you’ll “refuse to rule” unless a trigger is hit.
  • Outputs: Cadence + Update Template.
  • Checks: Check-ins focus on outcomes/risks/decisions, not task-by-task status.
  • 输入信息：时间线；团队常规流程；利益相关方需求。
  • 行动：设定沟通频次、更新格式以及你需要关注的内容（风险、决策、需求）。明确除非触发特定条件，否则不会干预执行。
  • 输出：沟通跟进节奏+更新模板。
  • 校验：沟通聚焦于成果/风险/决策，而非逐项任务的状态。

7) Review in the details without micromanaging

7) 把控细节但不微观管理

  • Inputs: Work artifacts; review points.
  • Actions: Review output quality via artifacts (docs, specs, results) and criteria. When the team is struggling with the right problems, step back. When it’s the wrong problem, intervene with clarity on outcome/guardrails.
  • Outputs: Review notes + decisions (approve/adjust/escalate).
  • Checks: Feedback is framed as “quality bar + constraints” (not “do it my way”).
  • 输入信息：工作产出物；评审节点。
  • 行动：通过产出物（文档、规格说明、结果）和既定标准评审质量。当下属在解决“正确的问题”时，退居幕后；当方向偏离时，明确重申成果目标与边界规则进行干预。
  • 输出：评审意见+决策（批准/调整/升级上报）。
  • 校验：反馈需围绕“质量标准+约束条件”展开（而非“按我的方式做”）。

8) Close the loop (debrief + “give away the Lego”)

8) 闭环收尾（复盘+彻底放权）

  • Inputs: Final deliverable; what happened; learnings.
  • Actions: Debrief what worked/what didn’t, update ownership maps, and explicitly acknowledge the new owner. Capture improvements to templates/guardrails.
  • Outputs: Debrief notes + next delegation candidates.
  • Checks: Ownership is durable (not “it snaps back to you” after delivery).
  • 输入信息：最终交付物；实际执行情况；经验总结。
  • 行动：复盘成功与不足，更新所有权归属，并明确认可新负责人。记录可优化的模板/边界规则。
  • 输出：复盘记录+下一批授权候选事项。
  • 校验：所有权需长期稳定（而非“交付后又回到你手中”）。

Quality gate (required)

质量校验（必填）

  • Run references/CHECKLISTS.md and score with references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 执行references/CHECKLISTS.md中的检查清单，并通过references/RUBRIC.md进行评分。
  • 必须包含：风险、待解决问题、下一步行动。

Examples

示例

Example 1: “Delegate discovery + recommendation for improving onboarding activation to my PM.”
Expected: delegation brief, decision rights (what PM decides vs escalates), context pack (data + constraints), weekly cadence, review plan for the final recommendation doc.
Example 2: “Delegate building a lightweight internal tool to an engineer, but I’m worried about security/compliance.”
Expected: guardrails + escalation triggers, clear non-negotiables, review points for design + launch readiness, and a debrief plan.
Boundary example: “Delegate ‘make the company strategy better.’”
Response: require a narrower outcome (decision to support, artifacts, time box) before producing the Delegation Pack.
示例1：“将优化新用户激活流程的调研+建议工作授权给我的PM。”
预期输出：授权简报、决策权限（PM可自主决策vs需上报的事项）、上下文包（数据+约束条件）、每周沟通节奏、最终建议文档的评审计划。
示例2：“将搭建轻量级内部工具的工作授权给工程师，但我担心安全/合规问题。”
预期输出：边界规则+升级上报触发条件、明确的不可协商项、设计+上线准备阶段的评审节点，以及复盘计划。
边界案例：“授权‘优化公司战略’的工作。”
回应：需先明确更具体的成果目标（如支持的决策、交付物、时间范围），再生成Delegation Pack。