Latest
AI’s Black Box Is Getting a Window. Somebody Still Has to Look Through It“It Stars C. Thomas Howell. No.” Why AI Gets Stuck in a LoopShould You Query or Self-Publish Your Memoir If You’re Not Famous?Judge the Writing, Not the Tool: What the AI Pile-Ons Get WrongThiago Ferreira: Thinkers, Not DoersYana Semova: Let AI Do the AdminLisa Hamilton-Smith: Unstoppable, AI AssistedSuperman Day: The $130 Contract Behind the CapeRaymond Chandler Day: The Novelist Who Started at FiftyJohn Steinbeck Day: The Reporter Who Wrote the NovelInternational Translation Day: The Invisible AuthorsMaya Angelou Day: The Dare That Became a MemoirNational Podcast Day: The Interview Is the Raw MaterialKurt Vonnegut Day: The Book That Took Twenty YearsTell a Fairy Tale Day: The Stories Everybody EditedHarry Potter’s Birthday: The Book Twelve Publishers MissedHarper Lee Day: The Draft Her Editor Saw ThroughGene Roddenberry Day: The Pilot Who Pitched the StarsRoald Dahl Day: Six Pencils and a Grudge Against Grown-UpsInternational Literacy Day: The Readers Books LoseJack Kerouac Day: The Scroll and the Last AddressElmore Leonard Day: Leave Out the Part Readers SkipEncourage a Young Writer Day: The Adult Who Read the PagesBack to the Future Day: The Script Where Everything Pays OffNational Library Lovers Month: The Building a Town Pays ForAlice’s Day: The Story Told on a Rowing BoatRobert E. Howard Day: The Texan Who Built ConanStephen King Day: The Daily Two ThousandEmily Dickinson Day: The Poems in the DrawerIan Fleming Day: Two Thousand Words a MorningFyodor Dostoevsky Day: The Novels Written Against the ClockZora Neale Hurston Day: The Ear She TrainedF. Scott Fitzgerald Day: The Masterpiece That FloppedElmore Leonard’s 10 Rules of Writing, and Which Ones I BreakShould Your Novel Have a Prologue? When a Cold Open Earns Its Place“People Who Use AI Deserve to Be Castrated”: When the Sentence Outruns the CrimeHow Famous Memoirs Were Really Written: What the Collaborators DidThe Bell JarOpen: An AutobiographyBeneath a Scarlet SkyFlorida RoadkillCampus BattlefieldLifeThe Phone Book: The Curious History of the Book That Everyone Uses But No One ReadsThe Sage of SagittariusDid I Ever Tell You This?: A MemoirPa’anAmerican SoldierIt Doesn’t Take a HeroMake Your Bed: Little Things That Can Change Your Life…And Maybe the World
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

The ethical concerns about AI are real, and not using the technology doesn’t solve them

TL;DR: Training data taken without consent, labor displacement, environmental cost and power concentrated in a few companies are all legitimate reasons people give for refusing AI. Refusing the technology entirely doesn’t follow from any of them, and the refusal usually has no effect on the underlying problems.

I take the ethical objections to AI seriously, and some of them are fully justified on the creators’ behalf. Writers had their work scraped without anyone asking them, and nobody should wave that away. What I can’t get behind is the idea that one professional refusing the tools fixes any of it. Refusal feels like a moral act. In practice it mostly removes the person with the conscience from the conversation that decides how people use this technology.

The ethical concerns, taken seriously

I want to engage with the ethical doubter position on its strongest version. The strong version goes like this.

AI companies trained their models on text and images scraped without permission from creators who never agreed to the use. The benefits flow to a few large companies. Costs flow to the workers whose labor the companies took and to the workers whose jobs the resulting tools will affect. Environmental cost of training runs is real and concentrated in regions that didn’t choose to host it.

The economic surplus from the technology will compound to a few firms in a few cities. The workers employers are asking to use the tools are the same workers whose displacement the tools are designed to enable.

That argument is coherent and has serious people behind it. I don’t think it’s correct in its strongest form, but the doubter who holds it is engaging with real problems. Where the position goes wrong is the conclusion it draws about what an individual professional should do with that diagnosis.

I don’t think it’s correct in its strongest form, but I think the doubter who holds it’s engaging with real problems instead of imagining them.
Share on X

What does individual AI refusal accomplish?

An individual professional refusing to use AI changes the trajectory of the technology approximately zero. The training has happened.

Models exist. Companies that built them have capitalization beyond what individual customer decisions can affect. The labor displacement concerns work at policy and labor-organizing levels. The environmental concerns are addressable through energy policy and data center regulation. Your refusal is a personal stance, which has its own value, but it’s not a lever on the underlying problems.

The closest analogy is quitting social media because of what it does to democracy and mental health.

Those concerns are legitimate, and quitting has real personal benefits for many people. It doesn’t change the platforms, the algorithms, the spread of misinformation or the effects on civic life. Individual refusal is a coherent personal practice. Treating it as a strategy for changing the technology buys moral satisfaction and leaves the problem exactly where it was.

Is AI training data an ethical problem?

The training data complaint is the most specific and legally fluid of the ethical concerns.

Writers had their work scraped without anyone asking them, and nobody should wave that away.

Courts in multiple jurisdictions are working out whether training on copyrighted material without licensing constitutes infringement, and the answers will shape how companies build the next generation of models. The question is open. Individual professionals can have legitimate positions on it. The professional uncomfortable using current models because of how companies trained them is taking a defensible stance. The defensibility doesn’t require pretending the question is settled in either direction.

The complication is that the professional who refuses on training data grounds usually doesn’t refuse other technologies built on similarly contested foundations. Most software stacks include open source components used in ways the original authors didn’t anticipate.

Most professional research depends on aggregating sources in ways the sources didn’t consent to. The internet itself runs on protocols whose creators imagined a different use than what emerged.

I lose patience with the loudest refusers over that inconsistency.

Somebody who types objections on a laptop full of open-source code, looks things up with search engines that indexed everybody’s work without asking, and posts it all to a platform that sells their attention owes readers an explanation of why AI is the line. Maybe there’s a good one. I’d like to hear it said out loud.

Selectively applying the training-data objection to AI but not to the rest of the professional stack is a position that needs to be argued explicitly instead of treated as obvious. A piece on the actual quality problem with AI takes the related concern about output quality seriously without resorting to the categorical-refusal frame.

Will AI displace writing jobs?

The labor concern is the most emotionally weighty and the most variable across professions.

Some workers will lose ground to AI tools. Others will become considerably more productive and capture the gains. Many will see their work change in ways that are neither pure loss nor pure gain. The distribution of those outcomes is uneven, hard to predict, and a real subject of policy debate.

The position that an individual professional should refuse AI because of labor concerns runs into the same problem as the training data version. The professional’s refusal doesn’t preserve the jobs that AI affects. Development continues regardless. The workers most affected are usually not the worker doing the refusing. The refusal is symbolic at best and self-defeating at worst, because the refusing professional sometimes ends up displaced by professionals who did engage with the technology.

That last outcome is the one I’d warn anyone about. The professional who refuses on principle gets no credit for the principle when the work dries up. Clients don’t ask why you’re slower; they hire someone who isn’t. A more useful position is to engage with the technology, develop real working judgment about it, and use that judgment to advocate within your industry and in policy conversations for how the technology should be governed. A piece on AI and the realistic labor picture covers the working version of this engagement.

What is the environmental cost of AI?

The environmental cost of AI training and inference is real and worth tracking. The numbers are also smaller than the rhetoric sometimes suggests, and they’re improving rapidly as hardware efficiency increases and energy mixes shift. Individual professional decisions about whether to use AI don’t meaningfully affect the environmental footprint, because the major commercial deployments of the technology and data center energy policy determine that footprint, and neither of those is downstream of individual customer choices.

The professional who’s concerned about the environmental cost of AI has better levers than personal abstention: supporting policies that require data centers to use clean energy, choosing AI vendors whose disclosure on energy use is transparent, advocating for reporting standards on AI carbon footprints. Those are the lever points where individual professional voice can matter, and the lever points are different from “don’t use the tools.” Individual refusal is a personal practice. The energy mix question is a policy and procurement question.

A worried professional who spends one afternoon pressing a vendor for its energy disclosures does more good than one who spends a year feeling virtuous about abstaining. Only one of those puts pressure on somebody who can change the numbers.

My take

Personal refusal changes nothing about training data, jobs or energy use. Development goes on without you, and the professional who refused gets no credit when the work dries up. Clients don’t ask why you’re slower. They hire someone who isn’t. If the ethics bother you, engage and push where it counts. One afternoon pressing a vendor for its energy disclosures does more than a year of feeling virtuous.

The more useful position for a thoughtful doubter

The thoughtful doubter has another option besides refusal, and the option is more demanding instead of less.

The option is to engage with the technology, develop working judgment about it, and use that judgment to push the industry toward better practice. Professionals who understand AI well enough to evaluate it are the people whose voices matter when companies decide how to deploy it, when policymakers write rules, and when norms get set in industries. The doubter who refuses has no voice in those conversations because they have no working knowledge.

The doubter who engages and disagrees has a voice because they have credibility.

That position is harder than refusal, because it means using a technology you have reservations about.

It’s also the more honest one, because the technology exists, companies will keep developing it, and whatever norms come out of the conversations professionals are having now will govern it. Walking away from those conversations hands the decisions to exactly the companies the doubter distrusts, and I suspect those companies are glad to see the critics leave. If your ethics are serious, stay in the room and make them uncomfortable.

From the author
The Birth of the Augmented Human by Richard Lowe

The Birth of the Augmented Human
Refusal leaves the ethics unsolved and you less capable. My book The Birth of the Augmented Human is about the path where AI amplifies thinking instead of replacing it.

Frequently Asked Questions

Are the ethical concerns about AI legitimate?
Yes. The training data question, labor displacement, environmental cost, and concentration of power in a few companies are all real concerns worth taking seriously. The legitimacy of the concerns doesn’t by itself imply that individual refusal is the right response.
What does refusing to use AI accomplish?
Personal moral satisfaction and a coherent personal practice. It doesn’t change the trajectory of the technology, the labor effects, the environmental cost, or the concentration of power. Those problems work at policy and industry levels that individual customer decisions don’t move.
Is using AI ethically defensible given the training data problem?
The training data question is open and being worked out in courts. A professional can have legitimate concerns about it. The same professional usually uses many other technologies with similarly contested foundations, so the objection needs to be argued explicitly instead of applied selectively to AI.
What happens to workers who lose jobs to AI?
The concern is real and the effects will be uneven across professions. Individual refusal doesn’t preserve the affected jobs. Better to engage with the technology and advocate within your industry and in policy conversations for how it should be governed, a more useful position than abstention.
What’s the better position for a thoughtful doubter?
Engage with the technology, develop working judgment, and use that judgment to push the industry toward better practice. Professionals with credibility on AI are the people whose voices matter when norms get set. Refusal removes you from the conversation.

The book on this: The Death of Thinking is 314 pages on what outsourcing judgment costs. That’s the question a thoughtful refusal is really trying to answer.

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

One comment
Was this useful?

Leave a comment