When the Task Disappears Into the Agent
Drucker’s question, Q1 2026’s answer
The social norms flip faster than the job descriptions.
Nobody decided to make Cowork the default. It happened the way habits always happen: one more Tuesday where opening Word to “write a report” felt slower than opening Cowork to “get the report done.” The preposition swap is the whole story.
It starts embarrassingly small. You point Cowork at a messy downloads folder, say “give me the quarterly board pack,” and walk away. You come back to a clean directory, a versioned deck, a model with working formulas and pivot tables already wired. Someone says, “That would’ve taken me half a day.” The second time, they don’t open Excel. Excel has become a limb Cowork moves, not a place anyone goes.
Drucker spent decades on one uncomfortable point: in knowledge work, the hard part is deciding what the task is. Execution is just what follows. The reason knowledge work was always hard to measure and manage was that the defining and the doing lived in the same body, at the same desk, in the same uninterrupted Tuesday. You had to figure out what the board pack needed before you could build it, and both steps looked identical from the outside: person, laptop, coffee.
Cowork is the first tool that actually separates them at the surface. You put the definition in: “prepare next week’s QBR from the past six months of calls, emails, and NPS.” Cowork handles the doing: reads the transcripts, mines the CSVs, drafts the slides, organizes the folders. The artifacts arrive without you inhabiting any application at all. What you typed was a decision. What came back was the execution of it.
That’s where the stakes live, not in the features list. Every time you hand a pattern to Cowork, you move a piece of your method out of your head and into a library the org can rerun without you. Drucker said the knowledge worker owns the means of production because the method is in their skull. In a Cowork-shaped org, the method is in a recipe file. The firm keeps it when you leave. Your leverage shifts from “I know how” to “I still control which problems are worth encoding and where the agent is not allowed to improvise.”
The social norms flip faster than the job descriptions. Once teams see that “give it to Cowork” reliably returns finished artifacts, manually building another status deck starts to feel like refusing to use the system. Performance reflects it. Time spent formatting or sorting reads as a failure to automate, not as diligence. Project templates stop listing “create Excel, create PowerPoint, write summary” as steps and collapse into one line: “configure Cowork with these inputs and constraints.” The unit of work has migrated from documents to delegated processes, and the thing people actually get judged on is whether their recipes run clean against dirty real-world data.
New grads arrive already inside that grammar. They don’t trade VLOOKUP tricks as status signals; they pass around Cowork setups and guardrails: the morning run that fires a dozen tasks before the first meeting, the weekly spec that keeps the pipeline report sane even when the CRM export is garbage, the constraint that stops the agent from inventing targets when finance hasn’t closed. The craft is no longer pushing cells and slides. The craft is specifying what you want precisely enough that the agent doesn’t improvise somewhere it shouldn’t.
Drucker’s three questions land differently in that world. “What is my task?” is harder when a one-sentence brief is enough to start an agent that touches every file on your machine. “What is my contribution?” is harder when the artifact exists before you’ve opened any application. “What do I insist on deciding myself?” is the only one worth fighting over, because it’s the only one the agent can’t answer for you.