Workers begin to "perform" AI efficiency gains: padding Skill counts, watering down weekly reports, and AI usage rate assessments
Employees at big tech companies are turning AI efficiency gains into a performance: some write "having AI transcribe half an hour of the boss's meeting recording" as "building a structured voice information workflow" and get rated as an excellent case, while others deliberately pick unimportant scenarios to package into Skills for reporting. A Visier survey shows that of 1,000 full-time US employees, 48% admit to exaggerating their AI usage frequency or expertise to colleagues or superiors. Some companies include AI usage rate in performance assessments, deducting 20% of performance pay for falling short of 70%, so employees churn out a pile of Skills nobody uses.
Topics
Body · AI translation
With just over two months left in 2026, big-tech employees are about to make it through a year dominated by AI.
At the start of the year, Jensen Huang's remark that "it would deeply unsettle me if an engineer earning $500,000 a year consumed less than $250,000 worth of tokens annually" set off the Tokenmaxxing wave. Everyone was using AI, everyone was burning tokens, and it seemed that if you used too few tokens, you weren't doing your job properly.
By June, big companies found that tokens were getting a bit too expensive to burn, and began to focus instead on the return on AI usage. This didn't reduce employees' AI FOMO (fear of missing out); it actually made it harder for them to "please" their bosses through AI use. They had to prove that AI was helping them work more efficiently, that what they delivered had to contain AI, and that every token they consumed was producing value.
To that end, some people wrote "having AI transcribe half an hour of the boss's meeting recording into text" as "building a structured voice-information workflow," and it was even rated an outstanding AI application case; some deliberately took unimportant work scenarios, turned them into Skills, and packaged them under impressive-sounding names to show the boss; and some big-tech PMs (product managers) used AI to do the work of RDs (R&D engineers), then had to ask their RD colleagues to redo it all over again.
This phenomenon is now increasingly common in workplaces at home and abroad. Not long ago, a survey involving the business-intelligence company Visier showed that among 1,000 full-time U.S. employees surveyed, 48% admitted to exaggerating their frequency of AI use or their AI expertise to colleagues or superiors.
01. To make my weekly report contain AI, I spent half an hour on a ten-minute task
Li Zhao | Born 1992, Hangzhou, product operations at an e-commerce company
March to May was truly intense. Our group had a usage ranking, and admin exported the data and sent it to the group chat every week. Back then, using AI wasn't about getting work done; it was about not falling behind on the leaderboard. I asked the girl ranked first how she did it, and she said she had AI write her annual plan before bed and didn't even look at it when it finished. I copied her: as soon as I got to my desk I had AI run "competitor monitoring," then I'd scroll short videos and check out entertainment gossip myself, and that counted as getting by.
In June the wind changed: no more looking at usage, only at output. Weekly reports had to show "AI efficiency cases," with data. I started figuring out how to pad the numbers. The most ridiculous time, I wrote "having AI transcribe half an hour of the boss's meeting recording into text" as "building a structured voice-information workflow," and this item was later rated an outstanding case. Another time, early this month, I was drafting a channel price-adjustment notice—originally a ten-minute job—but to make my weekly report contain AI, I had AI draft it. It made up a bunch of data for me, and in the end I dug out last year's Double 11 notice, tweaked it, and submitted that. But in the weekly report I still wrote "AI-assisted drafting."
Image source / pexels
Padding is padding, but the work still has to get done, and I've gradually worked out a method. Two monitors at my desk: AI running on the left, work on the right. For proposal-type work, I throw in the brief and wait for the framework, without repeatedly adjusting instructions—whatever it asks, I answer. While it runs the first section, I write the requirements for the second; when the second starts running, I go back and check the first section's results, and casually finish refining the third part—hours of continuous spinning. AI really can boost efficiency. Last Thursday, with more than forty customer-service complaints, I had it categorize them by issue and it produced a table in ten minutes. And organizing meeting minutes: right after the meeting, while everyone was just getting back to their desks, I'd already sent the minutes to the group chat.
But AI doesn't run on a fixed schedule—it could be thirty seconds or an hour. I've tried doing something else in the meantime, and halfway through an edit it finishes; I switch back to look at the result, then switch back again, and often forget where I was. Later I just scrolled my phone, watching progress while scrolling. During that period I clearly felt my focus declining—switching screens back and forth, exhausted by the end of the day but unable to say from what. I had to categorize my work: when doing A, resolutely don't use AI to do B; save small tasks like polishing for later and set aside one or two hours a day to handle them in a batch.
02. The demo I wrote was completely unusable, but my boss was very satisfied
Li Mo | 27, Beijing, product manager at a big internet company
I'm a product manager at a big internet company in Beijing, 27 this year, and I've worked at this company for two years.
At the start of the year the company began requiring everyone to do AI and write Skills. R&D colleagues were affected first, and then it spread to every position. Actually I'd used AI on and off before—writing copy, organizing requirements—it was at the "give it a try" stage.
Around March or April this year, our group leader talked to me, saying that in the future PMs who couldn't write code would quickly be eliminated, and required us all to learn to use AI to write code, to solve simple requirements ourselves as much as possible and not go to R&D for everything.
After that I did write some small demos and did some small UI designs. To be honest, none of it was really usable; when I gave it to my R&D colleagues, they still had to redo it—meaning no matter how lively my writing was, in the end they were the ones covering for me. But the boss was very satisfied. During that period I clearly felt that reporting and delivering became easier than before; anyway, whether the thing could actually be implemented was secondary—the posture of "you are using AI" was established first.
Image source / pexels
After June, our group changed a lot—both front-end and back-end had significant adjustments, and my reporting line changed too. The new leader made the assessment of AI output and efficiency gains much more detailed; the old approach of casually writing something myself and handing it to R&D colleagues to fix could no longer pass muster.
So I switched to a different approach to "AI efficiency." I wrote steps like requirement feedback, market research, and product frameworks into Skills—basically just some very simple page reading and organizing—and had AI handle each part, with the deliverables essentially coming straight from AI. There wasn't much of real value in all this; it was more about "performance."
For one thing, a lot of this work didn't need AI at all—doing it myself wouldn't have taken much time. For another, many of the requirements AI produced were hard for colleagues to actually push forward once they got them; they'd often find logic errors, and we'd have to hold another meeting to go over everything again. On the surface the process was running, but actual efficiency wasn't necessarily higher than before.
Still, doing it this way had its benefits: the Leader thought we were very busy, the AI workflow was set up, the process data looked good, and the reports looked good too.
My own judgment on this is that AI really can boost efficiency—especially in writing code and writing documents, where it genuinely saves time—but it can't always boost efficiency, and forcing it on actually creates chaos. And personally, I think the biggest problem is that once the Leader thinks your efficiency has improved, they want you to take on other people's work. The benefits of efficiency gains don't land on you; instead they become the basis for piling on more work, which is a losing proposition.
03. Under 70% AI usage rate and your performance review gets docked—we churned out a bunch of Skills nobody uses
Xiaonan | Post-95s event planner in Shenzhen
Later they even folded AI usage rate into performance reviews: if the usage rate didn't reach 70%, performance pay was docked 20%.
At first, nobody thought much of it—after all, AI really could boost our efficiency. Producing an event planning proposal used to take at least 3 days. Now with AI, a first draft can be done within a day. For miscellaneous work like competitor analysis and PPT creation, AI can help too, and it really did save a lot of time.
But gradually, things started to go wrong. The company launched an internal AI competition, seeing who could use AI to cover more work scenarios, build more workflows, and create more Skills. As long as you could prove you'd used AI to connect some part of the work process, it counted as an achievement.
At first, what people made really was useful—for example, Skills related to event planning could reduce some repetitive, trivial work.
But valuable scenarios are limited, after all, so to complete the tasks, people started competing on quantity. Some people specifically sought out unimportant work scenarios, made them into Skills, and packaged them under impressive-sounding names; others used AI to make a mini-program and, in their reports, showed off what problems they'd solved and how much time they'd saved.
Image source / pexels
I feel like everyone gradually developed a subtle tacit understanding. Compared with whether AI actually helped, being able to show visible results mattered more. After all, how many Skills you made and how many work scenarios you covered are easy to "fake," but how much time was actually saved and how many real problems were solved aren't so easy to measure.
One colleague used AI to quickly generate an event proposal, paired it with a polished PPT, and took it to report to the boss. The boss was very satisfied after seeing it, thought efficiency was especially high, and immediately told the people below to push forward according to the proposal. But when it came to execution, everyone discovered there were quite a few holes in the proposal and many practical issues hadn't been considered. In the end, it still had to be patched up and adjusted bit by bit by people.
What frustrated me even more was that AI's presence also made the number of revisions to proposals increase. Before, once a planning proposal was done, the leader would look it over, offer some comments, and after revisions it could move forward. Now the leader, after looking it over themselves, also hands it to AI for review. AI often comes up with a pile of revision suggestions—some genuinely valuable, but some not in line with reality—and we have to check, explain, and revise them one by one.
I find it quite contradictory. The boss wants AI to help the company save time, but we have to spend extra time participating in competitions to prove we really are using AI. We finally use AI to improve efficiency, only to take on more review, revision, and delivery tasks. Seen this way, using AI actually becomes a bad deal.
04. We act for the AI: articulate clearly, and smile so it can be heard
Wang Min | Post-95s salesperson at a software development company in Shanxi
Five months into this job, I've seen what "AI not adapting to local conditions" really means.
The company's main business is software development. It's been around for over a decade and has about 100 employees. The boss is over sixty, and his understanding of AI basically comes from marketing accounts. Last year he proposed an AI transformation, and at the start of this year it was directly upgraded to an annual strategy. After more than half a year, some business lines have doubled output after using AI, but more often than not, it's absurd.
So everyone started using their own tricks to "scrape together AI." For example, the day before yesterday they made a skill, yesterday they did a round of data cleaning, and today they did a full-lifecycle plan for a client from 0 to 1—the AI share got pushed all the way from 30% to 80%. Whether AI actually did the work doesn't matter; as long as it "participated," that's enough.
Weekly reports used to be written for the boss to read; now they've become a looping process. I send my thoughts to AI, AI writes the weekly report, I check it and send it to the boss, the boss uses AI to come up with a few questions and sends them to me, I send them to AI, and so on back and forth. The thing I use AI most for every week is having AI make up what I did with AI this week.
Image source / pexels
He thinks employees typing away at computers making proposals during the workday is slacking off. He always says you can't produce results by typing; you need to make more phone calls and communicate more. So an AI customer management system was put in place: calls are automatically recorded, AI listens in, summarizes, and gives suggestions, and a daily report is generated when the call ends.
Now employees on the phone at work look like they're "on camera." Say one wrong thing and the backend logs it; use a bad tone and AI gives suggestions; fail to close a deal with a client and the daily report is automatically flagged in red. The boss idly scrolls the app replaying communication records, and whenever he hears something that rubs him the wrong way, he screenshots it and tosses it straight into the big group chat. Every time we see a group message pop up, our backs go cold.
One day the boss came out of a meeting and said he wanted to build an internal AI bot, with employees at the core of an AI-driven overhaul, to solve document sharing and boost efficiency. The HR colleague followed online tutorials and uploaded all the attendance, performance, and payroll spreadsheets, and it was built in a day. Then someone in the company group chat asked about salaries, and the AI just dumped out the details.
That set off an explosion. Some people discovered pay disparities for the same role, some found their performance scores had been suppressed, and others dug through the entire company's salaries and found three names that were still being paid but had never once shown up for work. To everyone's surprise, the boss didn't publicly criticize HR at the next day's summary meeting—he actually praised her for her efficiency. But after the meeting, the boss contacted the AI company's tech team to add permission restrictions, and the system went back online.
AI is clearly a good thing, yet the more we use it, the more off it feels. We originally counted on it to save effort and boost efficiency, but instead we have to put on a show for it. In the end, what's exposed isn't a problem with AI—the payroll leak is the company lacking basic common sense about data permissions. Employees putting on a performance at work is the boss treating AI as a new surveillance tool. AI amplifies management itself: if processes are smooth, it amplifies efficiency; if there's a lot of suspicion, it amplifies internal friction.
Once I understood this, I actually felt relieved. Even without performance reviews, I still can't do without AI—making PPTs, writing planning documents, organizing files, it really does save me a lot of effort on these tedious chores. But anything that requires professional judgment, I absolutely never hand over to it.
05. What leadership wants isn't efficiency gains, it's the look of "AI for everyone"
Lin Zhou | post-00s, Guangzhou, software R&D engineer
A few days ago, a colleague I didn't know suddenly reached out to me, asking how to use a plugin I'd published on the internal plugin marketplace. I was actually pretty happy. After all, this was something I'd spent time researching, and someone actively using it meant it really solved a practical problem.
But my +1 (direct supervisor) didn't seem satisfied with just that.
Image source / pexels
I was a bit confused. The tool I'd figured out on my own really was useful, but everyone's work content and habits are different—why insist on using the same process? What was even stranger was that the veteran employees in the group who'd been working for more than five years didn't seem anxious at all. One veteran employee told me privately that he didn't really care.
Later, I figured it out. The core competitiveness of veteran employees lies in business experience and professional knowledge. To them, AI is just an auxiliary tool—use it however is convenient, since it isn't tied to performance anyway. What's really tied to AI is the +2 who called for the department's AI transformation, the +1 who actively responds, and the unlucky new employees assigned specific tasks—like me.
This also explains why +1 is so fixated on building SOPs.
Recently a few outsourced colleagues joined the department. I have a vague feeling that once this version's development wraps up, they'll probably leave. When the next project starts, new people will come in again. With staff turnover this frequent, the ideal management approach is naturally to standardize workflows so new people can get up to speed without much training. People can leave, but the skills stay.
I think the direction of AI development is personalization and customization. In the past, people adapted to tools; now tools should adapt to people, and everyone can build their own workflow according to their needs. But +1 seems to think AI can turn all business into SOPs. To put it bluntly, I think his idea is half wishful thinking and half performance. How much efficiency is actually improved may not be the most important thing—what matters is letting superiors see that the whole department is undergoing AI transformation.
It's just that I originally thought I was helping colleagues reduce repetitive work, and only later realized I might also be helping the company reduce its dependence on employees. What's more subtle is that this doesn't conflict with my personal interests—it may even benefit me. I can learn new technologies, accumulate project experience, and gain real sense of achievement.
I still enjoy doing AI efficiency work; it's just that after suddenly seeing clearly what management's possible motives are, there's an extra layer of unease in my heart. Now I finally understand why some people say a high moral sense makes you unfit for this company. The most uncomfortable thing isn't being forced to do something bad—it's clearly doing something you enjoy, only to discover it also serves a logic you don't agree with.
*Cover image from pixabay. At the request of interviewees, Li Zhao, Li Mo, Xiao Nan, Wang Min, and Lin Zhou are pseudonyms in this article.
This article is from the WeChat public account "Dingjiao" (ID: dingjiaoone), authors: Jin Yufan, Wang Hanxing, Lei Jing, Wang Lu, Chen Dan. Published by 36Kr with authorization.