惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

罗磊的独立博客
L
LangChain Blog
aimingoo的专栏
aimingoo的专栏
IT之家
IT之家
B
Blog
博客园_首页
博客园 - 司徒正美
有赞技术团队
有赞技术团队
博客园 - 聂微东
I
InfoQ
美团技术团队
GbyAI
GbyAI
阮一峰的网络日志
阮一峰的网络日志
H
Help Net Security
大猫的无限游戏
大猫的无限游戏
MyScale Blog
MyScale Blog
WordPress大学
WordPress大学
The GitHub Blog
The GitHub Blog
A
About on SuperTechFans
人人都是产品经理
人人都是产品经理
Microsoft Azure Blog
Microsoft Azure Blog
Engineering at Meta
Engineering at Meta
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Four Things That Can't Be Delegated
Amit · 2026-06-06 · via DEV Community

Amit

TL;DR

  • After systematically delegating research, drafting, synthesis, scheduling, and deployment to AI agents, exactly four things remain that structurally cannot be handed off — not "shouldn't," structurally can't.
  • The four: conviction (which hill is worth dying on), relationships (presence can't be outsourced), curiosity (noticing the strange thing nobody named yet), and high-stakes judgment (accountability requires a person who chose with full awareness of the tradeoffs).
  • Everything else — including most of what fills a knowledge worker's day — is execution: the conversion of a decision into output, and agents are extraordinarily good at it.
  • Most knowledge workers spend a small fraction of actual hours on the four irreducible things; agent delegation frees those hours but only if you don't fill them with more execution.
  • The question is not whether AI will replace knowledge workers — it's whether you'll show up in the work that's irreducibly yours instead of staying busy with what's comfortable and countable.

For several weeks, I've been pushing delegation as far as it goes — handing off research, drafting, synthesis, scheduling, formatting, triage, and deployment to AI agents. The goal was practical: find the floor. Find what's left when you systematically offload everything offloadable.

I found four things. Not things that shouldn't be delegated. Things that can't be.

This distinction matters. "Shouldn't" is a preference. "Can't" is structural. And these four are structural — the work either requires something an agent cannot possess, or the output is worthless without a human at the center of it.


The Four Things

Conviction. What's worth doing? Which problem matters enough to pursue? Agents can research every option, score them against criteria, rank them by expected value. They cannot tell you which hill is worth dying on. That judgment requires a point of view that was formed through experience, loss, and the accumulated weight of caring about something. Conviction is not analysis. It's a bet you've chosen to make with your finite time. Agents don't have finite time. They don't have anything at stake.

Relationships. Trust is built through shared context, vulnerability, and follow-through over time. An agent can draft the perfect email. It can read the history of a relationship and construct something plausible and warm. But it cannot replace the fact that you showed up when things were hard, that you remembered what mattered, that you were the one who made the call at the moment it cost something. Relationships are not content. They are a record of presence. You cannot outsource presence.

Curiosity. The most valuable question is the one nobody's asking yet. Agents answer questions brilliantly — with speed, range, and synthesis that no person can match. But they answer. They don't wonder. Curiosity is generative in a way that's different from search or retrieval — it's the act of noticing that something is strange, that a pattern doesn't fit, that a gap exists that nobody has named. That noticing happens unprompted, sideways, while you're doing something else. Agents don't have the sideways. They work the queue.

High-stakes judgment. When the blast radius is large and the decision is irreversible — a hire, a strategic pivot, a public commitment, a hard conversation — the human must own it. Not because humans are smarter. Because accountability requires a person who understood the tradeoffs and chose anyway. An agent can surface every consideration and present a recommendation. It cannot be responsible for what happens next. Judgment without accountability is just suggestion. Someone has to sign.


What This Actually Means

Everything else — research, formatting, scheduling, triaging, drafting, synthesizing, deploying — is execution. Important execution, in many cases hard execution. But execution: the conversion of a decision into output. That's what agents are extraordinarily good at.

Which means the practical question is not "will AI take my job." The practical question is: what percentage of your actual working hours are you spending on conviction, relationships, curiosity, and high-stakes judgment — versus execution?

For most knowledge workers, the honest answer is a small percentage. Most days are dominated by execution overhead: the reformatting, the scheduling back-and-forth, the summarizing of the thing that was already summarized, the chasing of inputs that should have been automated months ago.

That overhead is now, largely, delegable. Which means the hours it occupied are freed — and the question becomes what you do with them.

This is where the leverage question bites. If your job has been mostly execution, you now have two options: find the conviction, relationship, curiosity, and judgment work that's been crowded out — or fill the recovered hours with more execution because it's familiar and quantifiable.

Most people will fill. That's not a prediction about weakness; it's a prediction about organizational defaults. The work that gets rewarded visibly is usually execution. The work that creates long-run value — the right question asked, the relationship maintained, the judgment call made clearly — is often invisible until it isn't.


Reframing the Question

The question is not whether AI agents will replace knowledge workers.

The question is whether knowledge workers will learn to identify the work that's irreducibly theirs — and then actually show up there, consistently, instead of staying busy with the work that's comfortable and countable.

The agents are fast. They don't get tired. They don't have opinions about which meetings to take or which problems are worth the effort. They will execute whatever queue you give them.

What you put in the queue is still yours.