授权：把活交出去，责任留下来

什么时候该把活交出去？当另一个人能真正拥有一个有意义的成果，当这件事能练出有用的判断力，或者当你的注意力已经是瓶颈。留在自己手里的是：风险还界定不了的决定、对方在合规上不能接触的机密事项，以及只有你能做的管理动作。别只因为「今天我做得更快」就把活攥着。这个习惯能保证你下个季度还是那个瓶颈。

# Delegation screen
Outcome: What useful state will exist?
Repeatable: Will this kind of work happen again?
Judgment: Can I explain the decision boundaries?
Access: Can this person receive the required information and tools?
Risk: What is reversible, costly, regulated, or public?
Growth: Will ownership build a capability the team needs?

Delegate: monthly customer-risk review
Keep: final termination decision and private HR records

合适的人有够用的基础能力、有能想事的时间、找得到相关的人，也有在意这件事的理由。经验最丰富的那位往往早就满负荷了。风险可逆、支持到位的时候，最新来的人也可能是对的选择。要直接问对方还剩多少余量，别把沉默当成同意。所谓拔高，是往前迈一步，不是把人扔进完全陌生的地方。

Candidate     Relevant proof       Capacity     Support needed
Ari           ran last review      none         —
Mei           analyzed churn       4 hrs/week   first stakeholder call
Jon           wants exposure       6 hrs/week   data-access approval

# Copyable invitation
“I'd like you to own the July risk review because your churn analysis
showed the judgment this needs. It is about six hours over two weeks.
Before you answer, what would need to move for that to be credible?”

如果说「不」会带来惩罚，就别把这次派活叫成成长机会。哪些是硬要求、哪些可选、哪些现有工作要停下来，请如实讲清楚。

一次像样的交接要给出：想要的结果、原因、给谁用、相关历史、截止时间、约束、涉及的人、已知的坑，还有能用的原始材料。然后就停下。背景讲的是地形，不是每一步该踩在哪儿。让接手的人自己提路线。如果方法、措辞和会议安排全由你定，那你只是派出了体力活，工作还在你手上。

# One-page delegation brief
Result: identify the 10 accounts needing intervention this month
Why: customer-success capacity is limited to 10 recovery plans
Done by: draft Tuesday 15:00; final Thursday 12:00
Use: renewal risk, product usage, open severity-one issues
Do not use: protected demographic data
Stakeholders: Sam in Success; Inez in Data
Constraint: no customer contact before Sam approves the list
History: last list over-weighted ticket volume
Owner proposes: scoring method and review format

授权出问题，多半是权限没说清。「你来负责」能有五种意思。请指明适用哪一级：调研并汇报；给建议；征询后决定；决定后通知；在边界内自行行动。随着证据积累，把权限往上挪。有责任却没权限，那是个坑。

# Authority ladder
1. Research; bring facts. I decide.
2. Recommend with options. I decide.
3. Decide after consulting named people.
4. Decide, act, and inform me by the agreed time.
5. Act independently inside these boundaries.

This assignment: level 3
You may choose the scoring method after consulting Data and Success.
Escalate: use of new data, customer contact, or more than 6 hours of work.

「做好一点」不是标准。要给出：给谁看、支撑什么决定、需要什么证据、可接受的错误率、格式，以及一份好样例和一份差样例。把必须项和偏好项分开。如果你在交付之后才抛出藏着的偏好，那这次返工你也有一份责任。

# Definition of done
[ ] exactly 10 accounts, each with a one-sentence risk reason
[ ] source metric and date shown for every claim
[ ] Success and Data disagreements recorded, not silently averaged
[ ] no protected demographic data
[ ] spreadsheet opens without permission requests
[ ] recommendation fits on one screen for Thursday's decision

Preference, not requirement: use the previous color scheme.

质量不好描述的时候，就先看一小份样本。先审两行做完的，再让人去做五十行。一个好样例传递品味的速度，比一整页形容词快得多。

检查点的作用是拦住代价高的误解、解开卡住的决定、调整支持力度。它不是监视。把它放在方案提出之后、第一份有代表性的样本出来之后，以及不可逆动作之前。事先约好对方带什么来，这次会要产出哪个决定。检查点之间，让人安心干活。

Monday 14:00 — 15 min
Bring: proposed scoring model + two sample accounts
Decide: method is safe enough to run on all accounts

Wednesday 11:00 — async note
Bring: top 10, disputed cases, confidence, help needed
Decide: whether customer-success review can begin

Escalate immediately if: protected data appears, scope exceeds 6 hours,
or the Thursday decision is likely to slip.

反向授权，就是下属带着问题过来，管理者悄悄把这件事的所有权收了回去。别用一句「我来处理」回应所有不确定的问题。人还是那个负责人，你提供的是判断。问他观察到了什么、考虑过哪些选项、他建议怎么做、具体需要什么帮助。有时候诚实的答案是：卡住他的，是你一直没做的那个决定，那就赶紧做。

# When someone says “What should I do?”
“What decision are you trying to make?”
“What are the two best options you see?”
“What do you recommend, and what risk worries you?”
“Which part needs my authority or information?”

# Keep ownership explicit
“You still own the account list. I will get Data to restore your access
by noon. If it is not restored, bring me a reduced-scope recommendation.”

对照事先约定的结果去评审，不要对照你后来才想出来的那个版本。指出可观察的差距、它造成的影响，以及标准是什么。在给纠正方案之前，先问对方当时是怎么做出这个选择的。需要返工时，说清什么必须改、什么可以留、谁负责、什么时候再看。判断力值得夸的时候夸得具体一点，这样才可复制。

# Feedback script
“The source dates are missing on 7 of 10 rows. That means Thursday's
reviewers cannot tell whether the risk is current. Our done checklist
requires a metric and date for every claim. What made those dates hard
to include? Please keep the account choices, add the dates, and flag any
source older than 30 days by 10 tomorrow. You still own the final.”

# Specific praise
“You recorded the disagreement instead of averaging it away. That gave
us a real decision to make. Use that move again.”

如果工作达到了所有明说的标准，只是风格你不喜欢，那就把它叫做偏好，再决定改动值不值这个成本。不要私下把东西重写一遍。那会教出一个只等你那套隐形答案的人。

授权既要给普通错误留空间，也要给危险动作设硬停。要明确：哪些是可逆的试验、花钱上限、隐私规则、对外承诺、生产环境权限，还有停手的信号。远程协作时，把交接内容、权限级别、决定和检查点时间写在同一个能长期留存的地方。跨时区的沉默不等于同意。要说清你睡觉的时候谁能拍板。

# Safe operating boundary
You may: test scoring on internal data; revise weights; consult owners
Ask first: contact customers; add a data source; spend over $250
Never: export personal data; paste customer records into public tools
Stop and page: suspected data exposure or wrong-account contact
If I am offline: Priya may approve scope changes up to one day
Decision log: date · choice · owner · evidence · people informed

一次最短但够用的授权谈话，要覆盖：结果、原因、负责人、权限、完成的定义、约束、资源、检查点、上报条件，还有复述确认。跨天或者跨人的工作，请写下来。事情出问题的时候，除了看人，也要看这套机制。

# Copy, fill, send
OUTCOME:
WHY / WHO USES IT:
OWNER:
DONE BY:
DONE MEANS:
BACKGROUND / SOURCES:
AUTHORITY LEVEL: 1 research · 2 recommend · 3 consult+decide
                 4 decide+inform · 5 independent in bounds
MUST / MUST NOT:
RESOURCES AND ACCESS:
CHECKPOINTS + DECISIONS:
ESCALATE WHEN:
BACKUP APPROVER:
PLAYBACK: “Tell me your understanding and first move.”

# If delivery fails
protect impact → compare with stated done → ask what happened
→ own briefing/access failures → correct the gap → return ownership
→ change the system that allowed recurrence

最后表个态：授权既不是丢垃圾，也不是遥控操作。给一个人值得拥有的成果、能做真实选择的权限，以及让错误付得起代价的边界。责任你留着。至于「只有我这套做法才叫专业」这个幻想，放下吧。