The org chart we never named我们从未命名的组织结构图

There’s a small group at the top deciding why — why we exist, why this market, why now. Below them, a slightly larger group deciding what — what to build, what to ship, what to cut. And underneath both of those, the broad middle of the company, the part where the headcount actually lives — the how. Engineers, project managers, scrum masters, tech leads, engineering managers, program managers, who took the what and translated it into code, into tickets, into deployments, into release notes, into Slack messages in #releases.在顶部有一小群人决定“为什么”——我们为何存在，为什么选择这个市场，为什么是现在。其下是一稍大一些的团队决定“什么”——要构建什么，发布什么，削减什么。而在这两者之下，是公司广阔的中层，实际承载人数的地方——“怎么做”。工程师、项目经理、Scrum Master、技术负责人、工程经理、项目经理，他们把“什么”翻译成代码、工单、部署、发布说明、#releases 里的 Slack 信息。

The old org chart pyramid — small Why at top, larger What in the middle, broad How at the base where most of the headcount lives

I’ve been part of every layer. I’ve sat in the why room. I’ve run the what meetings. I’ve shipped a lot of how. I’ve also argued, for a long time and in a lot of rooms, that the middle of that pyramid was bigger than it needed to be — that leaders should be co-workers, not reviewers, and that managers who only managed were a tax the team paid for the privilege of having a status meeting. That argument never quite landed either. Same shape as the one I lost about tests — the cost was paid in slow, distributed ways that nobody in the room wanted to add up.我曾参与每一层。我坐过“为什么”会议。我主持过“什么”会议。我交付了大量“怎么做”。我也长期在很多会议上争论，中间的金字塔层级本应比现在小——领导者应当是同事，而不是审查者；仅仅管理的经理是团队为拥有状态会议而付出的税。这种争论也从未完全站住脚。就像我对测试的争论——成本以慢速、分散的方式被支付，而现场没人愿意把这些成本加总。

What’s on my mind a year into the agent shift is that the bill is finally getting itemised. And the line that’s getting cut is the one I’ve been pointing at for years.在代理转型一年后，我脑中浮现的是账单终于被细分了。而被削减的那一行正是我多年来一直指着的。

Most of what we did in the middle was translation.我们在中间所做的大多数工作都是翻译。

Business intent translated into product spec. Product spec translated into JIRA ticket. JIRA ticket translated into a branch name and a PR. PR translated into deployment. Deployment translated into a release note. Release note translated into a status update. Status update translated back upward into business language. Each step had its own ceremony, its own job title, its own meeting cadence. A whole industry of frameworks — Agile, SAFe, Spotify model, you name it — grew up around making the translation pipeline more efficient.业务意图翻译成产品规格。产品规格翻译成 JIRA 工单。JIRA 工单翻译成分支名和 PR。PR 翻译成部署。部署翻译成发布说明。发布说明翻译成状态更新。状态更新再向上翻译成业务语言。每一步都有自己的仪式、职位、会议节奏。围绕提升翻译流水线效率，形成了一整套框架——敏捷、SAFe、Spotify 模型，等等。

We were, mostly, glorified translators. I include myself in that. I include most of the best engineers I’ve worked with. The work was real and hard and required taste, but the shape of it was conversion. Take the thing in this language, output the thing in that language. Repeat.我们大多是被美化的翻译者。我把自己算在内，也把我合作过的大多数优秀工程师算在内。工作真实且艰难，需要品味，但其本质是转换。把一种语言的东西输出为另一种语言的东西。循环往复。

What AI actually ateAI 实际吃掉的东西

The agent conversation keeps getting framed as “AI replaces engineers” or “AI replaces customer service” or “AI replaces analysts.” All of those framings are slightly wrong. AI didn’t come for a job title. AI came for a task type, and the task type it came for was translation.关于代理的讨论常被框定为“AI 替代工程师”或“AI 替代客服”或“AI 替代分析师”。这些说法都有点偏差。AI 并不是针对某个职称而来，而是针对一种任务类型——翻译。

If your job was mostly converting one well-defined input into a well-defined output — natural language to SQL, requirements to code, ticket to PR, design spec to working component, log line to incident report, customer email to ticket — your task got compressed by an order of magnitude. Doesn’t matter what your title was. The task was translation. The task got cheap.如果你的工作主要是把一个定义明确的输入转换为一个定义明确的输出——自然语言到 SQL、需求到代码、工单到 PR、设计规格到可运行组件、日志行到事故报告、客户邮件到工单——你的任务会被压缩一个数量级。职称不重要，任务是翻译，任务变得廉价。

The two ends of the pipeline didn’t get cheap. Defining why — the business reason, the strategic call, the bet — is harder than ever, because the cost of executing on a bad why just dropped to nearly zero, which means more bad whys are going to ship, faster, with more confidence. Defining what — the product call, the cut decision, the “we will not build that even though we could” — is harder than ever, because the cheaper execution gets, the more options you have, and judgement under abundance is its own discipline.流水线的两端并未变便宜。定义“为什么”——业务原因、战略决策、赌注——比以往更难，因为执行错误的“为什么”的成本几乎降为零，这意味着更多错误的“为什么”会更快、更有信心地被交付。定义“什么”——产品决策、削减决定、“即使可以我们也不做”——也比以往更难，因为执行越便宜，可选项越多，在丰裕中进行判断本身就是一门学问。

The middle is what got eaten. And the middle is where most of the org chart lives.中间层是被吃掉的部分。而中间层正是组织结构图的大部分所在。

Hold that honestly. Not as a doom story. As a fact about the shape of work.老实说，保持这一点。不是在讲末日故事，而是关于工作形态的事实。

The manager who doesn’t contribute不做贡献的经理

Here’s a hard one, because it’s about people I’ve worked with and respected.这是个难题，因为它关系到我曾共事并尊敬的人。

A lot of engineering managers exist to coordinate translation. They run the standup. They unblock the ticket. They negotiate priority across teams. They write the status update. They translate engineering progress upward into business language and business priorities downward into engineering language.很多工程经理的职责是协调翻译工作。他们主持站会，解除工单阻塞，跨团队协商优先级，撰写状态更新，把工程进展向上翻译成业务语言，把业务优先级向下翻译成工程语言。

That work was real. It was load-bearing. The pipeline didn’t run without it.这项工作是真实且承重的。没有它，流水线根本跑不起来。

But if the pipeline itself is shrinking — if the layers between why and shipped code are collapsing because agents can carry more of the conversion themselves — then the manager whose entire job was coordinating the translators has a problem. The work that justified the role is dissolving.但如果流水线本身在收缩——因为为什么和已发布代码之间的层级在因代理能够自行完成更多转换而崩塌——那么整个工作只负责协调翻译的经理就会遇到问题。支撑该角色的工作正在消失。

I’ve watched two patterns emerge over the last year. One is denial — managers who quietly defend the rituals (the standup, the status meeting, the JIRA hygiene) because the rituals are what make the role visible. The other is the shift — managers who started writing again, designing again, defining again. Who picked up an agent themselves, not to prove a point, but because the org chart underneath them got smaller and the only way to stay useful was to be in the work.过去一年我看到两种模式。其一是否认——那些默默捍卫仪式（站会、状态会议、JIRA 卫生）的经理，因为仪式让角色可见。其二是转变——那些重新开始写代码、重新设计、重新定义的经理。他们自己挑起代理，并非为了证明什么，而是因为他们下方的组织结构变小，唯一保持价值的方式就是亲自参与工作。

I don’t think every manager needs to write code. I do think every manager needs to contribute — to the why, to the what, to the design of the harness, to the verification of the output. Coordination on its own is no longer enough. If a manager isn’t contributing to the why, the what, or the trust system that holds the how, it’s hard to say what they’re doing.我并不认为每个经理都必须写代码。但我认为每个经理都必须贡献——对“为什么”、对“什么”、对支撑系统的设计、对输出的验证。单纯的协调已不再足够。如果经理不对“为什么”、对“什么”或对维系“怎么做”的信任系统作出贡献，就很难说他们在干什么。

This isn’t a vendetta against managers. I’ve been one. I’ve hired dozens. The ones I’m most worried about are the ones who optimised so hard for being good at the translation pipeline that they forgot how to do the work that sat underneath the pipeline. The pipeline is getting smaller. The work underneath is getting bigger.这不是对经理的报复。我曾是经理，也招聘过数十位。我最担心的是那些为了在翻译流水线上表现出色而过度优化，以至于忘记了流水线下层的工作。流水线在变小，下面的工作在变大。

What the new team actually looks like新团队的实际模样

I’ve been sketching this on whiteboards with founders for months. Here’s the rough shape that keeps showing up.我已经和创始人们在白板上绘制了数月。以下是不断出现的粗略形状。

A small group of people defining why, mostly unchanged. The why layer was always thin and is going to stay thin, because conviction doesn’t scale linearly with headcount. You don’t need more people to decide why; you need a few people who decide it well.一小群人负责定义“为什么”，基本保持不变。为什么层一直很薄，并且会保持薄，因为信念不会随人数线性增长。决定“为什么”不需要更多人，只需要少数人把它决定好。

A larger group than before defining what. Not “product managers” in the old sense — not the ticket-writing, JIRA-grooming, sprint-planning archetype. People who can sit between the why and the agent, hold the context of what’s actually being built, and make the dozens of small calls per day about what “good” looks like. This is taste work. This is judgement work. This is what The Expensive Thing was about. The ratio of what people to how people is going to flip in the next two years, and most teams are not ready for it.比以前更大的团队负责定义“什么”。不是传统意义上的“产品经理”——不是写工单、梳理 JIRA、规划冲刺的那类人。是能够坐在“为什么”和代理之间，掌握实际构建内容上下文，并每天做出数十个关于“好”是什么的小决策的人。这是品味工作，也是判断工作。这正是《昂贵的事》所谈的内容。未来两年，负责“什么”的人数与负责“怎么做”的人数比例将会颠倒，而大多数团队尚未做好准备。

A much smaller group of people doing how — and the how people who remain are doing the hardest how work. Not ticket conversion. Architecture. Trust systems. Performance. The 5% of the codebase the agent shouldn’t touch unsupervised. The harness — the specs, the eval suites, the golden builds, the agent-of-agent review patterns. Someone has to design that harness. That someone is an engineer with deep judgement, and there are fewer of them on each team than there used to be, but each of them is doing dramatically more.更少的一群人负责“怎么做”——留下的“怎么做”人承担最艰难的工作。不是工单转换，而是架构、信任系统、性能。那 5% 的代码库不应让代理在无人监督的情况下触及。还有支撑系统——规格、评估套件、金版构建、代理‑代理审查模式。必须有人设计这些支撑系统。那个人是具备深度判断力的工程师，每个团队中此类工程师比过去少，但他们每个人承担的工作量大幅增加。

And then the agents themselves, doing the bulk of the conversion work. Writing the PR. Updating the doc. Filing the ticket. Drafting the release note. Reviewing each other’s outputs.然后是代理本身，完成大部分转换工作。编写 PR、更新文档、创建工单、起草发布说明、相互审查输出。

The team that’s left is smaller in headcount and broader in skill at every level. The middle thinned. The ends thickened. Coordination collapsed. Contribution went up.留下的团队在人数上更小，技能上更广。中层变薄，两端变厚。协调崩塌，贡献上升。

The new org shape — Why stays small, What grows into the dominant middle, How shrinks but gets harder, and Agents form the foundation doing the conversion work

Hands-on, redefined动手，重新定义

The phrase “hands-on” used to mean writing code. It still does, sometimes. But the deeper meaning is being in the work — close enough to the output that you can see when it’s wrong, opinionated enough about the input that you can define what right looks like.“动手”过去指写代码。它仍然有时指写代码。但更深层的含义是参与工作——足够贴近输出以发现错误，足够对输入有主见以定义正确的样子。

A founder writing prompts that drive an agent’s product roadmap is hands-on. A CTO designing the eval suite that gates production deploys is hands-on. A staff engineer specifying the contracts an agent must respect when modifying core code is hands-on. None of them are necessarily writing the code anymore. All of them are in the work. The principle was always the same — passing down comments is the cheap version of leadership, and the real version is showing what’s possible by doing it. The agent era doesn’t change the principle. It removes the alibi.创始人编写驱动代理产品路线图的提示词是动手。CTO 设计评估套件以把关生产部署是动手。资深工程师规定代理在修改核心代码时必须遵守的契约是动手。他们不一定再写代码，但都在工作中。原则始终不变——传递评论是廉价的领导方式，真正的方式是通过亲自实践展示可能性。代理时代并未改变这一原则，只是剥除了借口。

What’s not hands-on is approving JIRA tickets in batches. Running a status meeting where everyone reads off their updates. Writing a strategy doc that nobody operates from. Sitting in the layer above the work, translating between what the team did this week and what the business wants next week. That layer is shrinking. The hands-on layer is the layer that survives.不算动手的事情包括批量批准 JIRA 工单、主持所有人朗读更新的状态会议、写没人会遵循的战略文档、坐在工作之上的层级，在团队本周完成的工作与业务下周需求之间进行翻译。那一层正在收缩。动手层才是存活的层。

This is uncomfortable for a lot of senior people. It was uncomfortable for me, when I started really sitting with it during the sabbatical. There’s an emotional reflex to defend the role you spent a decade earning. But the role was the org chart — and the org chart is changing.这让很多资深人士感到不适。我在休假期间真正坐下来思考时也感到不适。人们本能地为自己辛苦十年争取的角色辩护。但那个角色本身就是组织结构图——而组织结构图正在改变。

What this means if you’re hiring这对招聘意味着什么

The hard thing to say out loud is also the first thing to get right: you’re going to hire fewer people. The team that does the same amount of work next year is going to be meaningfully smaller. Not because the people were bad. Because the translation layer collapsed. Every org that pretends otherwise is going to end up with the worst of both worlds — more tools, more headcount, slower output.大声说出来的难点也是首先要做好的一点：你将招聘更少的人。明年完成同等工作量的团队规模将显著更小。不是因为人才不好，而是翻译层已经崩塌。每个假装没有这种变化的组织最终都会两头不到岸——工具更多，人数更多，产出更慢。

Once you’ve accepted that, the rest gets clearer. Stop writing job descriptions that read like they were generated from a 2018 engineering ladder. The senior engineer whose pitch is “I can convert tickets to PRs faster than the next person” is going to be very confused, very soon, about what they’re doing every day. You need engineers who can define a harness, hold the line on quality, and design systems an agent can safely operate inside.一旦接受了这一点，其他就更清晰了。停止使用像 2018 年工程梯子那样的职位描述。那种“我能比别人更快把工单转成 PR”的高级工程师很快就会对自己每天在干什么感到困惑。你需要能够定义支撑系统、把关质量、设计代理能够安全运行的系统的工程师。

The standup-runner archetype of engineering manager is over. The managers who survive are the ones who contribute — to design, to definition, to the trust system. Coordination on its own doesn’t justify the seat anymore.负责站会的工程经理原型已经结束。能够存活的经理是那些在设计、定义、信任系统上有贡献的人。单纯的协调已不足以支撑其职位。

And hire more what people. Not product managers as ticket factories. People who can hold a thesis, define “good” in ambiguous situations, and operate the agent themselves rather than handing intent over a wall. The ratio of what to how is about to flip. Most teams aren’t ready for it.多招聘“什么人”。不是把产品经理当成工单工厂。招聘能够坚持论点、在模糊情境下定义“好”的人，并且自己亲自操作代理，而不是把意图交给墙那边的人。什么与怎么的比例即将翻转。大多数团队尚未准备好。

What this means if you’re an engineer这对工程师意味着什么

Don’t compete with the agent on translation. The agent will win. The agent will keep winning, faster, every quarter.不要在翻译上与代理竞争。代理会赢。代理会越来越快地赢，每个季度都是如此。

Pick up the work the agent can’t do. Define what “correct” means. Build the harness. Hold judgement. Take responsibility for outcomes the agent can’t be accountable for. Move toward the what and the why without abandoning the how — because the how people who survive are the ones who can still operate at the deepest layer when something genuinely hard breaks.承担代理做不到的工作。定义“正确”意味着什么。构建支撑系统。保持判断。对代理无法承担责任的结果负责。向“什么”和“为什么”前进，但不要放弃“怎么做”——因为能够在真正困难的情况下仍能在最深层操作的“怎么做”人才是能够存活的。

The middle is the dangerous place to be right now. Not because middle people are bad. Because the middle is where the translation work was concentrated, and the translation work is the work that’s going.中层现在是最危险的地方。不是因为中层的人不好，而是因为中层是翻译工作集中的地方，而翻译工作正是被吃掉的工作。

The work that’s left is more interesting and more valuable than the work that’s leaving. Defining the why and the what is more rewarding than running the standup. Designing the harness is more rewarding than approving the ticket. The shape of the team is changing because the shape of the work is changing, and the work is getting closer to what we always said we wanted — judgement-heavy, hands-on, outcome-owning. That’s not spin. It’s what happens when you strip out the translation layer and look at what’s underneath it.留下的工作比离开的更有趣、更有价值。定义“为什么”和“什么”比主持站会更有成就感。设计支撑系统比批准工单更有成就感。团队形态在变化，因为工作形态在变化，而工作正越来越接近我们一直想要的——重判断、动手、拥有结果。这不是夸大其词，而是剥离翻译层后看到的真实情况。

The org chart, finally组织结构图，终于

I started this post with the shape of the old org chart. Why at the top, what in the middle, how in the broad bottom layer, with a manager class running the seams.我在本文开头展示了旧的组织结构图形态。顶部是为什么，中层是什么，底层是广阔的怎么，经理类在缝隙之间运行。

The new shape is different. The why layer stays. The what layer grows. The how layer shrinks but gets harder. The manager class either contributes or disappears. The agents do the conversion work, with a harness around them.新形态不同。为什么层仍在。什么层扩大。怎么层收缩但更难。经理类要么贡献要么消失。代理完成转换工作，周围有支撑系统。

That’s not a layoff plan. It’s an evolution of what work is. And every leader I’m talking to is feeling some version of it, even when they can’t quite name it yet.这不是裁员计划，而是工作本质的演进。每位我交谈的领袖都感受到它的某种形态，即使他们还说不出名字。

The work was always the why and the what. We just spent thirty years pretending the how was the work, because the how was where the headcount was, and headcount was where the budget was, and budget was where the org chart was. The headcount is going to move. The org chart is going to follow.工作一直是为什么和什么。我们只是花了三十年假装怎么是工作，因为怎么是人数所在，人数决定预算，预算决定组织结构图。人数将会移动，组织结构图将随之而变。

The teams that figure out the new shape first are going to look unrecognisable to their competitors. Smaller. Stranger. More opinionated. Closer to the work. The harness from The Tests We Skipped is what makes this shape safe to operate — without it, the small team plus agents is a faster way to ship the wrong thing. With it, the small team plus agents is what the rest of the org chart used to look like before we built the translation pipeline on top of it.最先弄清新形态的团队将在竞争对手眼中变得面目全非。更小、更奇特、更有主见、更贴近工作。《我们跳过的测试》中的支撑系统让这种形态安全可操作——没有它，小团队加代理只是更快地交付错误的东西。有了它，小团队加代理才是过去组织结构图在我们在其上构建翻译流水线之前的模样。

That’s the shape I’m watching for. That’s the shape I think wins.这就是我在观察的形态。这就是我认为会赢的形态。

The agents are the deadline that finally makes the room move.代理是最终让整个房间行动的截止日期。