> ## Content Index > Fetch the complete content index at: https://www.ceo.com/llms.txt > Use this file to discover other available public pages before exploring further. # Am I Going to Be Replaced? - URL: https://www.ceo.com/blog/am-i-going-to-be-replaced/ - Published: 2026-02-19T00:37:00.000Z - Updated: 2026-08-14T00:39:21.000Z - Description: Chekhov wrote a two-page story about a clerk who dies of an apology. Every company adopting AI is busy staging it. - Author: CEO.com - Tags: #blog A minor bureaucrat named Tchervyakov is sitting in a theater when he accidentally sneezes on the back of a general's bald head. The general says it's fine. Don't worry about it. Tchervyakov apologizes. The general says forget it. But Tchervyakov cannot forget it. He goes home and tells his wife. The next day he shows up at the general's office to apologize again. The general waves him off. Tchervyakov comes back the following day. And the day after that. Each visit makes things worse. Each apology creates exactly the hostility he feared in the first place. Finally, the general, now genuinely furious, screams at him to get out. Tchervyakov walks home, lies down on his sofa in his uniform, and dies. That is the entire plot of Anton Chekhov's ["The Death of a Government Clerk."](https://www.livrosgratis.com.br/ler-livro-online-146860/the-death-of-a-government-clerk?ref=ceo.com) Two pages. A sneeze, a series of apologies, and a death. The story is absurd. It is also, if you lead people for a living, a useful read. What kills Tchervyakov is not the sneeze. It is not the general's anger, which only appears at the very end, manufactured entirely by Tchervyakov's relentless pursuit of forgiveness. What kills him is the gap between what is actually happening and what he believes is happening. The general says "never mind," and Tchervyakov sees a fiendish light in his eye. The general says, "I've forgotten it," and Tchervyakov reads it as barely concealed rage. He cannot receive reassurance because his fear is not about the sneeze. His fear is about his position in the world. He is a small man in a system that could crush him at any moment, and that knowledge has so thoroughly colonized his perception that he can no longer distinguish between reality and the story his anxiety is telling him. There is a version of this happening right now inside almost every company in the country. --- The $2 trillion software selloff made something concrete that had been abstract. J.P. Morgan called it the [largest non-recessionary drawdown](https://fortune.com/2026/02/10/stocks-2-trillion-software-wipeout-ai-bull-market/?ref=ceo.com) in software stocks in over 30 years. When markets began repricing entire companies built on software as potentially obsolete, the question stopped being theoretical. If the company itself might be worth dramatically less because of AI, what does that mean for the people inside it? For the engineer who spent a decade mastering a stack that a model can now approximate in seconds? For the marketing director whose team just got cut in half because a founder somewhere read a blog post about doing more with less? For the mid-level manager who has been hearing the word "efficiency" in every all-hands meeting for six months and knows, with the bone-deep certainty of someone who has survived previous rounds of corporate euphemism, that efficiency is what leaders say before they say layoffs? Every employee in your company has a question they are not asking out loud. Am I going to be replaced? Not by a competitor. Not by a restructuring. By a machine. They are not asking because they are afraid the answer is yes. They are also not asking because the culture has made it clear that this question is not welcome. You are supposed to be excited about AI. You are supposed to see it as a tool that will make you better at your job, not a tool that will make your job unnecessary. You are supposed to be an early adopter, a forward thinker, someone who embraces change. The anxiety you feel is a personal failing, a lack of vision, a resistance to the future. This is how organizations create Tchervyakovs. --- There is a pattern that keeps repeating in companies moving fast on AI adoption. Leadership announces a major initiative. The framing is relentlessly positive. Productivity. Efficiency. Competitive advantage. The technology is presented as purely additive. Everyone will be able to do more. Nobody talks about what "more" means when the headcount stays flat or shrinks. Nobody talks about what happens when a tool that lets one person do the work of three creates an obvious question about the other two. What happens next is predictable and invisible. The top performers leave first. This sounds counterintuitive. The best people should be the least threatened. But the best people are also the most mobile. They have options. When they sense that the ground is shifting under them, when they hear the language of optimization applied to human beings, when the all-hands meeting features a slide about "leveraging AI to do more with less," and nobody in leadership seems to notice that "less" means people, the best performers start taking calls from recruiters. They don't leave because they can't adapt. They leave because they don't trust the people in charge to value them through the transition. The people who stay begin to disengage. Not dramatically. Not in ways that show up immediately on a dashboard. They stop volunteering for new projects. They stop sharing ideas in meetings. They do their work competently and quietly and they stop doing the unseen work, the discretionary effort, the going above and beyond, the caring, that actually makes organizations function. Their bodies are at their desks, but their commitment has quietly migrated somewhere safe, somewhere that cannot be optimized away. The AI implementation then fails or underperforms. Because here is the thing that almost no one building the business case for AI wants to acknowledge: these systems depend on human beings. They depend on people who understand the work well enough to train the models, to check the outputs, to know when the machine is confidently wrong. They depend on institutional knowledge, on judgment, on the ten thousand small decisions that experienced people make every day without thinking. When those people check out emotionally, the AI does not magically fill the gap. It produces outputs that look right but aren't. It automates processes that needed human judgment at exactly the points where judgment was removed. It creates the illusion of efficiency while the actual quality of work quietly degrades. And leadership, having committed to the narrative, having built their board presentations around it, having tied their own compensation to the transformation, doubles down. The problem must be the technology. Or the implementation partner. Or the change management process. It is almost never recognized for what it actually is: a human problem created by the failure to treat it as such. --- None of this is an argument against speed. The technology is transformative. The companies that figure out how to use these tools well will outperform those that don't by enormous margins. Timidity is not the answer. But the technology question and the people question are the same question. You cannot answer one without answering the other. Right now, almost every leadership team is treating them as separate problems. The technology question gets the strategy decks, budget, and executive attention. The people question gets a vague reference to "change management" and maybe a lunch-and-learn about prompt engineering. Recall Tchervyakov. His tragedy is not just that he is afraid. It is that no one in a position of authority engages honestly with his fear. The general dismisses him. Forget about it. It's nothing. This is what most leaders do when employees express anxiety about AI. They wave it off. Your job is safe. AI is a tool, not a replacement. These reassurances are meant to be kind, but they function the same way the general's dismissals do in Chekhov's story. They tell the person that their perception of reality is wrong without ever addressing the conditions that gave rise to it. Tchervyakov is not afraid because he misread a social situation. He is afraid because he lives in a system in which his entire existence depends on the goodwill of those above him, where he has no real power, no real security, no real agency. His fear is rational even if his response to it is not. Telling him not to worry does not change the structure that produced the worry. It just tells him that his worry is not welcome. Your employees' fear of AI is also rational. They are watching the world change in real time. They are reading the same headlines you are. They see the layoffs framed as AI-driven efficiency. They hear the venture capitalists talking about how AI will let startups do the work of a hundred people with a team of ten. They know that "doing more with less" has a subject and an object, and they are pretty sure they are the object. Telling them not to worry is not reassurance. It is a signal that you either don't understand what they are going through or you don't want to talk about it. Either way, it breaks trust. --- What people need in a moment like this is not a guarantee that their jobs are safe. That guarantee would be a lie, and they are smart enough to know it. They need the truth. Not the catastrophic truth of "we're all going to be replaced." The real truth, which is harder: AI is going to change the nature of work in your company significantly; you don't know exactly how yet, and you are thinking about it seriously. Some roles will change. Some may be eliminated. New roles will be created. The specific shape of all this is still forming. They need transparency about how decisions will be made. When a leader says "we're investing in AI," what an employee hears is "we're investing in something that might replace me." The antidote is not reassurance. It is specificity. How will the company evaluate which roles are augmented by AI and which are displaced? What is the timeline? What does the company owe people whose roles are affected? Is the retraining real, with real resources behind it, or is it a token gesture designed to make the press release look better? Most importantly, they need leaders who stop treating them as a cost line item. The language of efficiency and optimization is the language of spreadsheets, and it is poison when applied to human beings. Every time a leader describes AI in terms of headcount reduction, doing more with less, or cost savings, they are telling their workforce exactly where they stand in the organization's hierarchy of values. They are telling them they are an expense to be minimized, not a capability to be developed. People hear this with extraordinary precision. They hear the thing you didn't say even louder than the thing you did. --- Chekhov's story ends with Tchervyakov dying on his sofa. Still in his uniform. That detail makes the story. He dies as the clerk. Not as a man. Not as a husband. Not as a human being with a life outside the hierarchy that consumed him. He dies in the costume of his function, because by the end, his function is all that's left. The fear ate everything else. Your people are not Tchervyakovs. Not yet. But they are sitting in the theater right now, watching you, trying to read the expression on your face, trying to determine whether the thing you said is what you meant, trying to figure out if the reassurance was real or if there was a fiendish light in your eye. What they see will determine everything that happens next. Not the technology. Not the implementation roadmap. Not the vendor you selected or the models you deployed. What your people see when they look at you.