AI Anxiety and the Output-Validator Workflow

Your team can want to use AI and still be worried about what happens to their jobs when it works. I wouldn't read those two things as a contradiction, because wanting a better way to do the work doesn't tell someone where they fit in the company afterward.

What I keep seeing is firms leaving that question unanswered while people start using AI through their coworkers. Then the work changes before anyone has properly decided how responsibilities should change with it.

Senior people receive finished drafts after the important choices have already been made, and they are still responsible for what reaches the client. They can approve it, send it back or repair it, but they weren't given a useful place in deciding what should have been made.

That is what I call an output-validator workflow, responsibility for the result without enough authority over the choices that shape it. My recommendation is to move that judgment earlier, explain what the company intends to do with the added capacity and give people paid time to learn the new work.

This is an operating pattern I have seen, not a claim that I have measured the anxiety of everyone working in it. The research gives us reasons to take lost decision power and job uncertainty seriously, and I want to keep that evidence separate from what I know from delivery work.

Take a marketing campaign as an example. This is an illustration of a pattern across firms, not one recorded client case.

Before production starts, somebody needs to choose the audience, the offer, the evidence and the promises the client can safely make. A senior marketer may know the history behind those choices, including a claim the client has already rejected.

Now suppose a junior employee can generate a complete campaign before that senior person sees the brief. The campaign looks ready, the team has spent time on it, and the senior marketer is asked whether it can go out.

Imagine the copy promises qualified leads in 30 days, but the client has no evidence for that result and has rejected guaranteed-outcome language before. The problem began before the writing, because the junior and the AI never received that boundary.

You can ask the senior person to fix the copy, and they can probably do it. But if the offer itself is wrong, checking becomes a return to decisions that should have been made before the campaign existed.

The junior wasn't careless for using the tool you wanted them to use. They were producing inside a brief that lacked information the firm already had, and management owns the job of getting that information into the work.

Nor is the senior person necessarily resisting AI when they keep sending it back. They may be trying to meet a responsibility you left with them after moving the decisions somewhere else.

There is a useful contrast here with a payment batch. AI can match invoices, flag possible duplicates and prepare the batch, while the controller decides whether the money leaves the bank.

In that case, final approval can be the important decision. The controller doesn't need to perform every earlier production step to retain real authority over the consequence.

A monthly client report can contain both kinds of work. AI can assemble the routine figures, but the person responsible for advising the client needs to decide why the margin changed and what action the report should recommend.

So the test isn't whether a person reviews something at the end. It is whether the person who carries the consequence controls the decisions that create it, wherever those decisions belong in the workflow.

That distinction matters because human review is necessary in plenty of work. This article is not an argument for removing it, or for requiring a senior person to touch every step so they can feel involved.

It is an argument for putting their judgment where it can still change the direction, instead of asking them to correct the direction after production has made it expensive to change.

The workplace surveys show why I would have this conversation openly. In EY's October 2025 survey of more than 1,100 US desk workers at large companies, 84 percent were eager to embrace agentic AI in their role, while 56 percent worried about their job security alongside agents.

That is not a survey of small service firms, and it doesn't establish that the people in my marketing example felt the same way. It does show that eagerness and concern can exist in the same workforce, so an adoption number isn't enough to tell you whether the team understands the plan.

The same EY survey found that 83 percent said most of their knowledge of agentic AI was self-taught. There is something worth noticing there, people are putting effort into learning, but the company may still be leaving them to work out how that learning changes their job.

Through a franchise network's delivery data, I have watched hundreds of service firms adopt AI, often with use spreading from one colleague to another before a coordinated company effort arrives. That gives people access to useful tools, but not necessarily a shared agreement about the work.

One person thinks a tool is allowed, another thinks client data cannot go into it, and the person checking the result is not sure which parts the AI did. Those are decisions the firm should make, rather than leaving each employee to negotiate them under a deadline.

In Slack's June 2024 Workforce Index, 37 percent of desk workers said their company had no AI policy. That was a multinational survey, not a current count of policies in US service firms, but it is another example of use and company guidance failing to arrive together.

I would not assume that writing a policy resolves job anxiety. People also want to know what the owner intends to do if the company can produce the same work in less time.

Are you trying to serve more demand, improve quality, change roles or reduce staffing? You may not know the final answer yet, but you can explain what you will measure, who will decide and when the team will hear the next decision.

EY reported a 30-point difference in workers reporting productivity gains for their teams, 92 percent where the organization clearly communicated its AI agent strategy compared with 62 percent where it didn't. This is survey evidence, not proof that communication alone caused the difference.

I still think communication belongs in the implementation plan. If the team has to guess what success means for their own jobs, you have left a consequential part of the change unmanaged.

There is a retention concern as well. In the American Psychological Association's 2023 Work in America survey, 46 percent of workers worried about AI said they intended to look for another job, compared with 25 percent of workers who weren't worried.

That measures intention, not actual departures, and it doesn't prove AI worry caused anyone to leave. For an owner, it is a reason to ask what the experienced people you depend on understand about their future before assuming they will stay through the transition.

The immediate cost is easier to see in the work. A campaign gets produced around the wrong offer, a senior person reopens the brief, and somebody has to make it again, often while new drafts keep arriving.

BetterUp Labs and Stanford Social Media Lab's September 2025 research found that 40 percent of surveyed US desk workers had received low-quality AI-generated work in the previous month. Respondents spent about two hours resolving an incident, on average.

The study calls this workslop, work that looks finished but leaves someone else to recover the substance. It did not test the output-validator workflow I describe here, so I use it as evidence of downstream work, not as a measured cost of this specific design.

The authority question has research behind it too. A 2026 Technology in Society paper on AI fear of missing out at work, using OECD workplace-survey data, linked perceived loss of decision-making autonomy with that fear and identified retained human oversight as a protective condition.

That doesn't prove a particular campaign workflow creates anxiety, or that moving a brief meeting will cure it. The narrower point is that whether people retain decision power matters, and you can inspect that in the work your firm assigns.

So in the marketing example, I would put the owner or account lead on the business goal and the senior marketer on the audience, offer, evidence and claim boundaries before production starts. The junior and AI then have freedom to produce within those decisions.

Give the junior a chance to make the choices as well. Before opening the tool, ask them to write the audience, the offer, the evidence they would use and one direction they would reject, then compare that with the senior person's reasoning.

That is AI training for employees in the context of the job. Learning which button produces copy is useful, but learning why a plausible campaign should not ship is the part they need if their role is going to grow.

The senior person has to explain the correction rather than silently repair it after hours. When the junior sees which assumption was wrong and why, the next attempt can begin with better judgment instead of just a better prompt.

I don't have a measured reduction in versions or review hours from that change. The recommendation addresses the missing information directly, but you would need to count your own rework before claiming a financial result.

A separate 2026 study of 424 employees in Kunming, China found that information literacy weakened the relationship between generative-AI use and job insecurity in its model of psychological distress. That was a cross-sectional study, not an experiment assigning paid training.

So I am not presenting it as proof that a training program will reduce anxiety in a US consultancy. My recommendation is to pay for the learning time because you are changing the work and asking people to become competent at it, that is a business responsibility rather than a private evening project for each employee.

I would put the first training dates in a one-page rollout plan, alongside the workflow owner and the decisions that stay with people. The plan should also say how you will evaluate any capacity the AI frees.

You could set a defined learning period before making AI-related staffing cuts, with 90 days as one possible starting point. That is an example to consider against your cash and delivery needs, not a measured standard or a promise you should make if you cannot keep it.

During that period, look at demand, review time, rework, quality and revenue per person. You need to know whether the whole job has improved and whether there is useful work for the released capacity, not only whether staff report writing faster.

My preference is to use that capacity against demand first, then retrain people and move them into work the business needs before considering cuts. I have seen firms retain experienced teams, adjust responsibilities and train people for new functions, but I did not run a controlled network-wide comparison proving a universal result.

And if the company doesn't yet know what it can afford, say that plainly. Give the team a decision date and the criteria rather than a reassuring promise that disappears at the next budget meeting.

The limits of this advice matter. Most of the US surveys cover broad workforces or large employers, the academic evidence is not a direct study of this workflow in US service firms, and I don't have employee testimony establishing the emotional effect of one observed case.

What I can tell you is where I have seen the work go wrong, important choices arrive after AI production, and senior people inherit the corrections. Before telling those people to get more comfortable with AI, look at the next brief and make sure they have the authority to shape the work they will answer for.