If you prefer, here is the author delivering the essay.
Seventy percent.
Thanks for reading The Long Game by Dr. Venki Padmanabhan! Subscribe for free to receive new posts and support my work.
That’s the number a billion-dollar CEO dropped in Fortune this week. Not in a footnote. Not in a caveat. As his central thesis.
Tanmai Gopal runs PromptQL, a Bay Area AI unicorn that helps Fortune 500 companies deploy artificial intelligence. He has seen, from the inside, what happens when the most powerful technology in a generation meets actual business reality. And his conclusion is that seventy percent of the effort required to make AI useful relies entirely on unwritten knowledge that exists only in human heads.
Not the code. Not the model. Not the data pipeline. The human.
The knowledge that lives in conversations. In judgment calls. In the instinct a twenty-year veteran has when something feels wrong before the data says so. In relationships that took years to build. In context that nobody wrote down because nobody asked and nobody thought it mattered.
Gopal said you fundamentally cannot train a system on this. It changes too fast. It’s too fluid. Too human.
This should be a liberation. Someone with a billion dollars of market credibility just told the world that without human intelligence, the most sophisticated AI on the planet is seventy percent useless.
Then he named the future of the human worker.
“Our job as humans and people is that we are now context gatherers instead of just workers.”
And there it is.
Context gatherers.
Your seventy percent—your judgment, your relationships, your hard-won knowledge—isn’t yours to deploy. It’s yours to donate. To collect the raw material of your own intelligence and feed it into a system that accrues returns to capital.
This is not a liberation philosophy. This is the most sophisticated extraction framework I have heard in thirty-six years of manufacturing. And it is dressed up as empowerment.
I need to be precise about what I mean by extraction, because the word gets thrown around loosely.
Extraction is when you take value from the person who creates it and transfer it to someone who didn’t. It’s when a steelworker’s thirty years of metallurgical knowledge gets captured in a process manual, the worker gets laid off, and the company sells the manual’s output as intellectual property. The worker created the value. Capital captured it. The worker got a severance check. Capital got a revenue stream.
“Context gathering” is that play’s white-collar update.
Here’s what Gopal is actually describing, stripped of the aspirational language: The AI doesn’t work without the human’s knowledge. The human’s job is now to transfer that knowledge to the AI. Once the AI has it, the human’s contribution is to go get more.
At no point in this framework does anyone ask: If the human’s context is worth seventy percent of the AI’s value, shouldn’t the human receive seventy percent of the AI’s return?
Last week I wrote about the SaaSpocalypse—the trillion-dollar software selloff triggered when Wall Street realized AI could do what SaaS tools help humans do. The market’s question was blunt: if the AI can do the task, why do we need the tool?
This week’s Fortune article asks the next question: if the AI can do the task but needs human context to function, what is the human’s role?
Gopal’s answer: context gatherer.
My answer: that’s the wrong question.
The right question is not “what role does the human play in the AI system?” The right question is “what role does the AI play in the human’s work?”
That is not a semantic distinction. It is the difference between an economy that uses humans to serve machines and an economy that uses machines to serve humans. Every dollar of return, every career trajectory, every community’s survival depends on which framing wins.
Manufacturing already ran this experiment. We have forty years of data.
When American manufacturers decided in the 1980s that the worker’s job was to serve the machine—to monitor it, feed it, clean up after it—they got a ninety percent automation failure rate and six point six million destroyed jobs.
When Honda, Toyota, and the Royal Enfield I helped turn around decided that the machine’s job was to serve the worker—to amplify their intelligence, extend their reach, remove the drudgery so the human could focus on judgment—they got twentyfold profit growth and JD Power Gold awards.
Same technology. Same factories. Same workers. Different directionality.
Gopal got something right in that article. He said the Silicon Valley doomsday predictions are self-projection. He said tech people assume their experience applies to everyone.
What he didn’t notice is that he’s doing the same thing. He’s projecting a Valley framework—extract the value, scale the platform, minimize the human cost—onto every worker in every industry. He’s telling a salesperson in Cleveland and a plant operator in Wooster and a nurse in Memphis that their job is now to gather context for the AI.
No. Their job is to be brilliant at what they do. The AI’s job is to make their brilliance go further.
There’s a practical alternative to the context-gathering model, and it’s not theoretical. It has two parts.
First: put the AI in the worker’s hand as a power tool. Not “capture their context for the system.” Let them wield it. Let the frontline operator use AI to diagnose a production fault in thirty seconds instead of three hours. Let the salesperson generate proposals at ten times the speed. Let the nurse cross-reference symptoms against the latest research in real time. The human remains the protagonist. The output belongs to the worker who created it, not to the platform that processed it.
Second: when that amplified output generates more revenue, share it back. Contribution-linked compensation. If the operator’s AI-amplified diagnostics save the company two hundred thousand dollars in scrap, the operator sees that in their paycheck. If the salesperson’s AI-amplified proposals close thirty percent more deals, the salesperson sees that in their commission. And you reinvest in further training so the worker becomes more valuable, not less.
This isn’t charity. This is what we do with every other appreciating asset. We maintain equipment. We invest in intellectual property. We protect real estate. We share in the returns they generate.
The moment the appreciating asset is a human being, the instinct reverts to extraction. Get the knowledge out. Encode it. Negotiate the salary down.
The Fortune article quotes Ed Meyercord, CEO of Extreme Networks, saying the choice is: “You can do a lot more with less, or you could do more with the same, or you could do a lot more with a little more.”
He framed this as a neutral menu. It isn’t. The first option is extraction. The third is investment. They lead to completely different futures for completely different people.
Here’s the part that should make you angry.
Gopal told Fortune his team was frustrated with a mediocre engineer. He said, and I’m paraphrasing: “It’s more expensive to talk to you than to do it myself with AI.” He offered this as evidence that AI will replace mediocre workers.
Let me offer a manufacturing translation.
That “mediocre engineer” was probably never given the context they needed to be excellent. They probably weren’t trained to Gopal’s standard. They probably weren’t developed, coached, or invested in. And now the CEO is publicly celebrating that it’s cheaper to replace them with a machine.
I have seen this scene play out on factory floors for decades. A worker underperforms. Management blames the worker. Management buys a machine. The machine fails because it turns out the worker was compensating for upstream problems nobody bothered to diagnose. The worker is gone. The machine doesn’t work. And management buys another machine.
The ninety percent automation failure rate is not a technology problem. It’s a leadership problem. And “context gathering” is the latest vocabulary for avoiding it.
Gopal closed his Fortune interview by warning that the only workers who need to fear for their jobs are those who are “refusing to grow.”
I’ve heard that line before. I heard it in Detroit in the 1990s, when auto executives said the workers who lost their jobs just didn’t adapt fast enough. I heard it in Lordstown, when GM closed the plant and said the community should have diversified. I hear it every time a CEO blames the workforce for a failure of leadership.
“Refusing to grow” is a convenient diagnosis when you control the greenhouse.
The workers at Royal Enfield didn’t refuse to grow. They were never asked. When we asked, they transformed a company from the edge of extinction into a case study in human-led turnaround. The workers at Lansing Grand River didn’t refuse to grow. They were given the tools, the trust, and a share of the outcome. They built the best cars in America.
Growth is not a worker problem. It’s a deployment problem. And deployment requires leadership willing to do something much harder than building an AI agent: sharing power, sharing knowledge, and sharing returns with the people who actually create the value.
The intelligence you need is already in the building. Already on the payroll. Already paid for.
Stop gathering it. Start deploying it.
Dr. Venki Padmanabhan is Plant Manager at Advanced Drainage Systems and author of “Already Paid For: Why Unlocking Frontline Intelligence Beats Automating Workers Away.” He previously served as COO/CEO of Royal Enfield and COO of Ather Energy, with thirty-six years of manufacturing leadership across three continents.
Subscribe to The Long Game for weekly essays on deploying the intelligence you’ve already paid for
Thanks for reading The Long Game by Dr. Venki Padmanabhan! Subscribe for free to receive new posts and support my work.
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit thelonggameforall.substack.com