WIRED reports that workers at three major publishing houses say large language models are being used for publicity, cover art, back-cover copy, and emails. The report also describes employee resistance, with some executives pushing junior staff to become champions for the technology.
That is a publishing-industry story, but it offers a practical lesson for small and medium businesses. AI adoption is not just a software decision: how leaders explain its purpose, choose its uses, and involve the people doing the work can determine whether it helps or creates distrust.
Why business owners should care
Many businesses first encounter AI as a quick way to draft social posts, summarize meetings, write customer emails, or create images. Those can be sensible experiments. But employees may see the same tools differently if they arrive without a clear explanation of what is changing, what remains their responsibility, and why the business is using them.
A marketing coordinator may worry that AI-written copy makes their skills less valuable. A designer may ask who is accountable when a generated image is off-brand or resembles someone else’s work. A customer-service employee may reasonably ask whether they are expected to send AI-generated replies without reviewing them. These are practical questions about quality, responsibility, and jobs, not necessarily resistance to technology itself.
The publishing report is also a reminder that AI can affect creative and customer-facing work, not only back-office administration. When a business uses AI in areas closely tied to its voice and reputation, an unreviewed output can do more harm than the saved time is worth. A generic sales email, inaccurate event announcement, or poorly chosen visual can signal to customers that nobody paid attention.
This does not mean small businesses should avoid AI. It means they should not mistake tool access for an implementation plan. A sensible rollout begins with a defined task, a named owner, and a clear review process.
Start with useful, lower-risk work
Choose repetitive work where a person already makes the final decision. An office manager might turn rough meeting notes into draft action items. A sales team might use AI to organize research before a call. A marketing employee might generate headline options, then select and edit one.
These uses keep judgment with the employee while reducing blank-page work. They also let the business assess whether the tool is actually saving time or simply moving work into editing and fact-checking.
For teams deciding where to begin, our guide to free AI meeting-note tools for small businesses offers one focused use case. The larger point is to choose work with a visible process and an easy way to check the result.
Set boundaries before sharing accounts
Write down a short set of rules in plain language. State what employees must not paste into public AI tools, including customer records, financial details, confidential contracts, passwords, or unreleased plans. Clarify whether AI output requires human review before it reaches a customer, supplier, or the public.
Also decide which tasks remain human-led. A small firm might allow AI to draft internal documents but prohibit it from making pricing promises, generating final legal language, or answering sensitive customer complaints. The right rules vary by business, but ambiguity rarely helps.
A one-page policy is enough to start. It should identify an owner employees can ask about new use cases instead of leaving each person to make a judgment under time pressure.
Bring the people doing the work into the test
The people closest to a workflow usually know its bottlenecks, exceptions, and customer sensitivities. Ask what takes too long, what errors recur, and where a first draft would help. Then invite a small group to test one tool for a limited period and report what happened.
Be direct about the goal. If the purpose is faster turnaround, say so. If it is to reduce repetitive formatting so staff can spend more time with customers, explain what that should look like. Vague promises that AI will transform the business can create more anxiety than clarity.
Measure results with simple evidence: time spent, number of revisions, error rate, and user feedback. If a tool creates extra checking or makes work sound less like the company, stop or adjust the test. A pilot that does not work is useful information.
For a structured way to identify appropriate workflows, an AI readiness audit for small business operations can help separate practical opportunities from tasks that need more preparation.
The PAD Take
Choose one repeatable, low-risk workflow and run a 30-day AI pilot with the employee who performs it, rather than buying broad access and hoping people find uses. Put a short data-handling and review policy in place before the pilot starts, and require human approval for customer-facing work. At the end, compare time saved and quality with the old process, then expand only where the evidence supports it.