Tag Archive | Red Teaming

From Draft to Publish — The Full Workflow

By Cheval John | Vallano Media
This article was created with the assistance of artificial intelligence.
The final version was reviewed, edited and fact-checked by the author


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

A draft can look finished long before it is ready to publish.

That is one of the biggest lessons I have learned from working with AI.

The writing may be clean.

The structure may work.

The grammar may be correct.

The headline may sound strong.

The article may even feel complete.

But publication requires more than a good draft.

It requires a process.

A draft has to survive verification.

Challenge.

Editing.

Quality control.

And one final decision:

Is this actually ready to go out into the world?

That is what the full workflow is designed to help me answer.

But there is an important distinction.

“Completing the workflow is not the same as completing it well.”

A checklist cannot guarantee good journalism.

The value comes from the judgment exercised inside every stage.

The Draft Is a Starting Point

By the time I reach the first complete draft, a lot of work has already happened.

The research has been gathered.

The evidence has been organized.

The story has taken shape.

The first version exists.

That feels like progress.

It is.

But the draft is not the finish line.

It is the point where the next stage begins.

Now the question changes from:

“Can I write this?”

to:

“Can I defend this?”

That is where the editorial workflow becomes essential.

Step One: Check the Claims

Before I think about style, I look at the substance.

What factual claims am I making?

Which ones are central?

Which ones are current?

Which ones are sensitive?

Which ones depend on a source I need to revisit?

Which ones sound more certain in the draft than they did in the research?

The goal is not to verify only the obvious numbers and dates.

It is to inspect the statements the reader is being asked to believe.

That includes interpretation.

Causation.

Context.

Attribution.

Comparison.

The stronger the claim, the stronger the evidence needs to be.

Step Two: Go Back to the Sources

The next step is source verification.

I open the documents again.

I check the original quote.

I confirm the number.

I reread the section of the report.

I look at the official record.

I make sure the source actually supports the sentence I wrote.

This can feel repetitive.

That is part of the point.

The draft is a transformation of the research.

Something can change during that transformation.

A qualification can disappear.

A number can lose context.

A sentence can become stronger.

A quote can be shortened in a way that changes its meaning.

Going back to the source reconnects the prose to the evidence.

Step Three: Run the Truth Pass

The truth pass asks a broader question:

What in this draft might be wrong, misleading, incomplete or overstated?

I look at the article differently during this stage.

Not as the writer.

As the skeptic.

What would I challenge if someone else wrote this?

Which sentence makes me hesitate?

Which claim depends on an assumption?

Which section needs another source?

Which statement might be technically accurate but missing important context?

Sometimes the answer is:

Nothing significant.

Sometimes the truth pass sends me back into research.

That is not a failure.

That is the workflow working.

Step Four: Red-Team the Story

Once the factual foundation is solid, I try to break the article.

This is where the red-team stage comes in.

I ask:

What is the strongest challenge to the central argument?

What evidence could weaken the conclusion?

What might a knowledgeable critic question?

What context is missing?

What is the weakest part of the story?

Does the headline promise more than the article proves?

AI can help generate those challenges.

But I do not accept them automatically.

Some critiques are useful.

Some are irrelevant.

Some are simply wrong.

The goal is not to obey the red team.

The goal is to expose the story to resistance.

Step Five: Decide What Survives

The red-team stage creates another decision point.

What actually needs to change?

A weak claim may need another source.

A sentence may need softer wording.

A section may need more context.

A dramatic headline may need to come down.

A paragraph may need to disappear completely.

And sometimes the story survives the challenge exactly as written.

That matters too.

The goal is not endless revision.

It is identifying material weaknesses.

Then fixing the ones that matter.

Step Six: Edit for Voice

Once the reporting survives the challenge, I focus on the writing.

Does it sound like me?

Does the rhythm work?

Is the article direct?

Is it repetitive?

Did AI make the language too formal?

Too generic?

Too cautious?

Too dramatic?

Are the strongest lines still there?

Has anything become polished at the expense of specificity?

This is where I try to make the article sound finished without making it sound manufactured.

The writing should become clearer.

Sharper.

More readable.

But still mine.

Step Seven: Read for Meaning, Not Just Grammar

Grammar matters.

So does punctuation.

But one of the most dangerous editing mistakes is concentrating so much on the sentence that I stop checking what the sentence actually means.

A small wording change can alter:

causation,

certainty,

timing,

attribution,

or scale.

“Led” is not the same as “won.”

“Reported” is not the same as “confirmed.”

“After” is not the same as “because of.”

A cleaner sentence is not automatically a more accurate sentence.

So after the voice pass, I read again for meaning.

Step Eight: Editorial Quality Control

Then comes the final QC pass.

This is where I stop developing the story and inspect the complete product.

Names.

Dates.

Numbers.

Quotes.

Attribution.

Headline.

Graphics.

Disclosure language.

Formatting.

Anything that might create a problem after publication.

This is also where production begins to overlap with editorial work.

The article itself can be correct while something around it is wrong.

A graphic may contain an error.

A caption may overstate the story.

A headline may be stronger than the evidence.

A link may go to the wrong source.

The entire publication package can affect how the journalism is understood.

Step Nine: Inspect the Graphic

AI-assisted graphics deserve their own check.

The visual may look excellent.

That does not mean it is finished.

I look for:

incorrect text,

strange anatomy,

misleading symbols,

factual mistakes,

unlicensed or inappropriate third-party visual elements,

and anything that changes the meaning of the story.

But visual quality control is bigger than catching an extra hand or a misspelled word.

A visual can be technically clean and still imply something the reporting does not support.

The same principle applies to the graphic as the article:

Do not approve it just because it looks polished.

Look at what it actually communicates.

Step Ten: Lock the Manuscript

Eventually, the editing has to end.

That is when I lock the manuscript.

Locked means the article has completed the required editorial stages.

The reporting has been checked.

The claims have been tested.

The writing has been edited.

The QC pass is complete.

It is ready for production.

Locked does not mean perfect.

It does not mean the article can never change.

New evidence may emerge.

A late source response may change the story.

An error may become visible only after publication.

If that happens, I should correct or update the work.

A strong workflow reduces risk.

It does not eliminate the possibility of correction.

Locked simply means I have reached the standard required to publish responsibly with the information available to me.

Step Eleven: Build the Publication Package

The article is only one part of what the audience sees.

The full publication package may include:

the headline,

main graphic,

tags,

disclosure,

social copy,

preview text,

links,

and sometimes a teaser for what comes next.

Each element needs review.

If the article is careful but the social post exaggerates it, the publication can still mislead.

If the headline is accurate but the graphic creates a false impression, there is still a problem.

And every derivative asset should be checked against the verified story itself.

Not against another derivative asset.

A caption based on a social post based on a summary of the article creates opportunities for meaning to drift farther from the original reporting.

The evidence remains the reference point.

Version Control Is Editorial Control

AI-assisted workflows can produce a lot of versions.

Several drafts.

Several headlines.

Several graphics.

Several social posts.

Several rewritten paragraphs.

That creates another risk.

Publishing the wrong one.

The strongest version is useless if an outdated draft reaches the website.

The corrected graphic does not help if the earlier version is uploaded.

The accurate headline does not matter if an abandoned option gets scheduled.

“Version control is part of editorial control.”

I need to know which manuscript is locked.

Which graphic is final.

Which headline is approved.

Which copy is actually being published.

That may sound administrative.

It is also editorial.

Step Twelve: Final Human Approval

At the end of the workflow, one decision still belongs to me.

Publish?

That sounds simple.

But it carries everything that came before it.

Do I trust the sourcing?

Do I understand the evidence?

Did I challenge the story?

Did I review the AI assistance?

Does the writing sound right?

Does the headline fit the reporting?

Does the graphic work?

Is there anything I would hesitate to defend after publication?

Final approval matters only if I am genuinely willing to stop the process.

If “Publish” is inevitable no matter what I find, then the final review is ceremonial.

Meaningful human oversight requires the authority to say:

Not yet.

If something is wrong, I go back.

If the work is ready, I publish.

That final approval matters because of the decisions that led to it.

The Workflow Can Move Backward

The full process is not perfectly linear.

A red-team pass can send me back to research.

Editing can reveal a factual question.

QC can uncover a problem in the headline.

A graphic can expose that the concept itself is unclear.

New evidence or a late source response can change the story near the end of the process.

The arrows sometimes move backward.

That is normal.

A workflow should not trap the work in a rigid sequence.

It should give the work checkpoints.

Places where I know what question I am supposed to ask next.

Deadlines Change the Pace, Not the Responsibility

Real journalism does not always happen under ideal conditions.

Breaking news moves quickly.

Live sports move quickly.

Deadlines compress the available time.

Staffing may be thin.

The workflow has to function in that environment too.

That may mean some stages happen quickly.

Several stages may overlap.

The level of review may depend on the risk of the story.

But deadlines should not erase the steps that protect accuracy.

Speed can change how I execute the workflow.

It should not change what I am responsible for.

The Workflow Is Not the Journalism

This is important.

The workflow is not the thing that makes the journalism good.

The journalism still depends on:

good reporting,

strong evidence,

sound judgment,

fairness,

context,

clarity,

and accountability.

A checklist cannot replace those things.

A workflow simply creates a structure around them.

It makes it harder to accidentally skip an important step.

That is useful.

But process is not proof.

A completed checklist does not guarantee a correct article.

Completing the workflow is not the same as completing it well.

The thinking still matters.

The Workflow Becomes Faster With Practice

There is another benefit.

The more often I use the workflow, the faster it becomes.

I know what to look for during the truth pass.

I know what kinds of questions work during red-teaming.

I know where graphics often fail.

I know which parts deserve more scrutiny.

That familiarity reduces friction.

But it should not reduce skepticism.

The process can become faster.

The judgment should not become automatic.

The More Automation, the More Important the Checkpoints

As AI-assisted workflows become more capable, some steps may become more automated.

That can be useful.

But automation creates another question:

Where does human judgment still have real authority?

If the system automatically summarizes the research, drafts the article, proposes the headline, generates the graphic and prepares the social copy, the workflow may look efficient.

It also creates more places where an early error can travel downstream.

The more automated the workflow becomes, the more important it is to know where a human can inspect, challenge and stop it.

Automation should not make responsibility harder to locate.

Speed Is Not the Victory

One of the easiest things to measure is time.

How fast did the draft happen?

How quickly did the article get published?

How many minutes did the workflow take?

Those numbers can be useful.

But speed is not the victory.

The real question is:

Did the workflow help produce something I can stand behind?

Sometimes that takes ten minutes.

Sometimes forty minutes.

Sometimes several hours.

Sometimes the correct answer is:

Not ready yet.

That is still a successful outcome.

AI Changes Where the Work Can Happen

AI does not remove the work.

It changes where some of the work can happen.

Less time may go into producing the first draft.

AI can assist with the more repeatable and support-oriented parts of the process.

That creates the possibility of reallocating more attention toward:

verification,

challenge,

comparison,

editing,

and judgment.

But that redistribution is not automatic.

Saving twenty minutes does not guarantee I will spend those twenty minutes verifying a source.

I still have to make that choice.

AI creates the opportunity.

The journalist decides how to use it.

The Full Workflow Is Really a Series of Decisions

Research.

Draft.

Truth pass.

Verification.

Red-team.

Voice edit.

Quality control.

Production.

Publish.

Those stages look like tasks.

They are really decisions.

What is true?

What matters?

What needs evidence?

What deserves doubt?

What should stay?

What should go?

What sounds right?

What is ready?

AI can help at almost every stage.

But it cannot take ownership of those decisions.

That remains human.

Before I Hit Publish

The final button is the easiest part.

Everything before it is the journalism.

The research.

The verification.

The challenge.

The editing.

The judgment.

The refusal to publish something just because it looks complete.

That is what the workflow protects.

Not perfection.

Responsibility.

So my final question is not simply:

“Does this look finished?”

It is:

“Have I done enough to stand behind it?”

And one more question follows:

“If this is challenged after publication, can I explain how I know what I published?”

When the answer to both is yes, then I hit publish.


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

From Draft to Publish-Ready: A Practical Editorial Workflow

By Cheval John | Vallano Media
This article was created with the assistance of artificial intelligence.
The final version was reviewed, edited and fact-checked by the author


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

A draft is not a finished article.

That sounds obvious.

But artificial intelligence makes the difference between the two easier to forget.

AI can produce polished language quickly.

It can organize ideas.

It can summarize research.

It can suggest structure.

It can even make a rough argument sound complete.

And that creates a dangerous illusion.

The article looks finished.

So the writer begins treating it as finished.

That is why I needed a workflow.

Not a prompt.

Not a shortcut.

A workflow.

A repeatable process that takes a draft through research, verification, challenge, revision, editorial judgment and final approval before publication.

That process became one of the most important changes in how I work with AI.

But there is an important warning from the beginning.

“A workflow does not guarantee accuracy.”

It creates deliberate places where errors, weak evidence and poor judgment have a better chance of being caught.

The quality of the work still depends on what happens inside those stages.

The Draft Is Only the Beginning

Before AI, a rough draft often looked rough.

The unfinished work was visible.

Sentences needed rewriting.

Transitions were missing.

Notes remained in the copy.

The weakness of the draft was easier to see.

Generative AI changes that.

A first draft can arrive looking clean.

The paragraphs may flow.

The grammar may be correct.

The tone may sound professional.

But polished writing does not mean finished journalism.

The draft may still contain:

unsupported claims,

missing context,

weak sourcing,

overstatement,

incorrect assumptions,

unclear attribution,

or conclusions stronger than the evidence.

The surface can look complete while the reporting underneath remains unfinished.

That is why I stopped treating the first AI-assisted draft as something close to publication.

It is simply the next thing that needs to be examined.

My Workflow Starts Before the Draft

A good editorial process does not begin with writing.

It begins with the question.

What am I trying to establish?

What evidence would support it?

What do I already know?

What do I need to verify?

Which sources should I find?

What would change the direction of the story?

AI can help organize those questions.

It can help identify gaps.

It can help create a research plan.

But in my workflow, I still decide what the story is actually about.

That matters because a weak question produces a weak workflow.

If I start with the wrong premise, moving faster through the process does not solve the problem.

It only gets me to the wrong destination sooner.

Stage One: Research

The first stage is evidence.

I gather the material that can support the story.

That may include:

official records,

statistics,

transcripts,

interviews,

reports,

news coverage,

or firsthand observations.

AI can help me organize that material.

It can compare documents.

It can identify names, dates, contradictions and patterns.

It can suggest follow-up questions.

But the research stage has one non-negotiable rule:

“AI output is not the source.”

If the AI gives me a fact, I still need to know where that fact came from.

If it summarizes a document, I still need to inspect the document.

If it gives me a quotation, I need the original quotation.

If it gives me a statistic, I need the original data.

Research is where evidence enters the workflow.

Everything afterward depends on the quality of that evidence.

Stage Two: Draft

Once the research is organized, I move into the draft.

This is where AI can save a considerable amount of time.

I can use it to help organize the structure.

I can test different openings.

I can explore different ways to arrange sections.

I can use it to help turn notes into readable prose.

But I do not ask AI to decide what the story means.

That decision remains mine.

The draft is a construction stage.

The goal is not perfection.

The goal is to create something complete enough to examine.

That distinction matters.

If I expect the first draft to be perfect, I may spend too much time polishing sentences that later need to disappear.

If I treat the draft as provisional, I can focus on building the argument first.

Then I can test it.

Stage Three: The Truth Pass

The next stage is what I call the truth pass.

This is where the draft stops being treated primarily as writing and starts being treated as a collection of claims.

I ask:

Which statements are factual?

Which ones need evidence?

Which are interpretation?

Which depend on current information?

Which could be misunderstood?

Which are stronger than the evidence allows?

Then I verify.

Some claims are easy.

A date can be checked.

A score can be confirmed.

A public document can be opened.

Other claims require more judgment.

A historical interpretation may need multiple sources.

A causal claim may require stronger evidence.

A quotation may be accurate but misleading without context.

The truth pass is not simply:

“Did I make a factual error?”

The better question is:

“Can I defend what this sentence is asking the reader to believe?”

That changes the way I edit.

Stage Four: Source Verification

Verification deserves its own stage because it is easy to confuse research with verification.

Finding information is not the same as proving it.

During verification, I trace important claims back to their strongest available evidence.

I open the source.

I read it.

I confirm the date.

I examine the context.

I check whether the source actually supports the wording in the article.

I look for independent confirmation when the claim warrants it.

But the existence of a verification stage does not automatically make the journalism verified.

“The quality of the verification matters more than the existence of the checkbox.”

Opening one link is not enough if the claim requires deeper scrutiny.

Finding one citation is not enough if several websites are simply repeating the same underlying source.

A citation tells me where to look.

It does not tell me whether the claim is correct.

This stage is where weak evidence becomes visible.

Sometimes the sentence survives.

Sometimes it becomes more cautious.

Sometimes it disappears.

The evidence decides.

The Stages Can Overlap

The workflow may look linear when written down.

Real journalism usually is not.

Some claims are verified before the first sentence is drafted.

Others emerge during the writing and send me back to research.

A red-team pass may uncover a missing source.

Editing may expose a factual statement I did not realize needed verification.

That is normal.

The stages are useful because they create discipline.

They are not a claim that journalism always unfolds in a straight line.

The workflow moves forward.

Sometimes it also loops backward.

Stage Five: Red-Team the Story

Once the major claims have been checked, I challenge the article.

This is the red-team stage.

I ask AI to look for:

weak arguments,

unsupported inferences,

missing context,

overstatement,

plausible alternative interpretations,

and headline problems.

But I do not accept every criticism.

AI can be wrong.

It can manufacture a counterargument simply because I asked it to challenge something.

It can give too much weight to a weak objection.

It can misunderstand the article.

So the red-team stage has two parts.

First:

Challenge the story.

Second:

Challenge the challenge.

The goal is not to obey the AI.

The goal is to expose the article to resistance.

Then I decide which criticism matters.

Every AI-Assisted Stage Can Introduce Error

This is another reason the workflow matters.

AI errors are not confined to the draft.

AI can misread research.

It can produce an incomplete summary.

It can suggest a structure that exaggerates one part of the evidence.

It can overlook contradictory information.

It can recommend a headline that is stronger than the reporting.

It can create a graphic with a factual or visual problem.

That means every stage where AI helps is also a stage where its output may need to be checked.

The system is assisting the workflow.

It is not exempt from the workflow.

Stage Six: Voice and Editing

Only after the argument has survived verification and challenge do I focus heavily on the writing itself.

Now I ask:

Does this sound like me?

Is the structure clear?

Is the article repetitive?

Is the language stronger than necessary?

Are the transitions doing their job?

Did AI introduce generic language?

Did the draft flatten uncertainty?

Did it make the article sound too polished, too formal or too predictable?

This stage matters because AI can make almost everything sound competent.

Competent is not the same as distinctive.

Journalism should still have a voice.

The writing should reflect the journalist’s judgment, rhythm and priorities.

AI can help improve the prose.

It should not erase the person behind it.

Stage Seven: Editorial Quality Control

The quality-control pass asks a different question:

“Is this ready to publish?”

At this point I am no longer trying to reinvent the argument.

I am inspecting the complete product.

Headline.

Names.

Dates.

Statistics.

Attribution.

Links.

Captions.

Graphics.

Disclosure language.

Formatting.

Repeated ideas.

Anything that could have slipped through the earlier stages.

This is where small mistakes get caught.

And small mistakes matter.

A deeply reported story can still lose credibility because a name is misspelled.

A headline can undermine careful reporting by overstating the conclusion.

A production element can introduce an error that never existed in the manuscript.

A graphic, caption, tag or disclosure can create its own problem.

Production is not separate from editorial accuracy simply because it happens near the end.

Stage Eight: Lock the Manuscript

At some point, the editing has to stop.

That is why I use the word:

“locked.”

A locked manuscript means the substantive editorial process is finished.

The article has been researched.

Verified.

Challenged.

Edited.

Reviewed.

It is ready for production.

That does not mean the article can never change.

If new evidence appears, I can correct it.

If I discover an error, I should fix it.

Locked does not mean untouchable.

It means the article has completed the workflow required for publication.

That distinction helps me avoid endless editing.

There is always another sentence I could adjust.

Another word I could change.

Another version I could consider.

At some point, responsible work has to become published work.

Stage Nine: Production

The manuscript may be locked, but publication still requires production.

The article has to be placed on the website.

The headline has to fit.

The graphic has to work.

Tags have to be added.

The disclosure has to appear.

Links have to function.

The page has to look right.

This is where the workflow expands beyond writing.

Publishing is not just about the manuscript.

It is about the complete package the reader sees.

AI can help with graphics, metadata, captions and formatting.

But those elements still need review.

A strong graphic with a factual, contextual or visual error is not finished.

A strong article with broken formatting is not finished.

The workflow does not end when the final sentence is written.

It ends when the published product has been checked.

The Workflow Is Not a Certification System

There is another danger once the process becomes familiar.

I can start believing that because I completed every stage, the article must be correct.

That would be a mistake.

A checklist is a safeguard.

It is not proof.

I can perform a weak truth pass.

I can miss something during verification.

The red team can overlook the real weakness.

The final QC can fail.

The purpose of the workflow is not to make mistakes impossible.

It is to create repeated opportunities to catch them.

That is a meaningful difference.

Familiarity Can Become Complacency

A repeatable workflow should reduce unnecessary cognitive load.

It should not reduce skepticism.

Once the process becomes familiar, I can move through it much faster.

That is useful.

But familiarity creates its own danger.

I can begin clicking through the stages mentally.

Truth pass?

Done.

Red team?

Done.

QC?

Done.

That turns editorial discipline into ritual.

The stage matters only if I am actually doing the thinking the stage requires.

Efficiency should make the process easier to execute.

It should not make the process automatic in my head.

Not Every Story Needs the Same Amount of Process

The workflow also needs proportion.

A short game recap does not require the same depth of review as a major investigative article.

A routine announcement does not carry the same risk as an accusation.

A feature based on public records may require different verification from breaking news.

The stages remain useful.

The intensity changes.

Responsible AI use should not mean turning every story into an exhausting bureaucracy.

The goal is not maximum process.

The goal is appropriate process.

Higher risk deserves more scrutiny.

Lower risk can move faster.

And some high-risk journalism may require safeguards beyond my normal workflow.

That could include additional independent reporting, another editor, legal review or subject-matter expertise.

A personal workflow should never become an excuse for believing one person and one AI system can adequately handle every kind of story.

Speed Is the Result, Not the Standard

One of the most interesting things I have learned from using this workflow is that speed becomes a byproduct.

Once the stages are familiar, I can move through them quickly.

Research is organized faster.

The draft develops faster.

Weak claims are easier to find.

The red-team process is repeatable.

The quality-control checklist is familiar.

That can dramatically reduce production time.

But speed is not the standard.

A ten-minute workflow is useful only if the article is actually ready.

If the story needs another hour of verification, then it needs another hour.

If a source has not responded, the workflow cannot manufacture the answer.

If the evidence is incomplete, AI cannot make it complete.

The purpose of the workflow is not to publish faster at all costs.

It is to reduce unnecessary friction while protecting the steps that matter.

The Human Is Still Directing the Process

This chapter brings the earlier lessons together.

The journalist remains responsible.

AI output is not evidence.

Human oversight has to mean something.

The story should be challenged before publication.

Now those ideas become a workflow.

AI may help at nearly every stage.

But it does not own the process.

I decide what question to pursue.

I decide what evidence matters.

I decide whether the claim is supported.

I decide which criticism requires action.

I decide whether the writing sounds right.

I decide when the article is ready.

And ultimately, I decide whether to publish.

That is what directing the workflow means.

From Draft to Publish-Ready

The most important change AI made in my work was not simply that it gave me faster drafts.

It forced me to think more deliberately about everything that happens around the draft.

Research.

Verification.

Challenge.

Revision.

Judgment.

Quality control.

Publication.

Those stages existed before AI.

But AI made the need to define them more obvious.

Because when a machine can produce polished language in seconds, the journalist needs a process that separates polished language from publishable journalism.

The workflow creates the places where human judgment must be exercised.

But the workflow itself does not provide that judgment.

The quality of the decisions made inside it still determines the result.

That is what turns a draft into something ready to publish.


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

Make AI Challenge the Story

By Cheval John | Vallano Media
This article was created with the assistance of artificial intelligence.
The final version was reviewed, edited and fact-checked by the author


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

One of the least useful things artificial intelligence can do for a journalist is agree with everything.

That may sound strange.

Most people want tools that help them.

They want answers.

They want suggestions.

They want reassurance that the work is good.

But journalism does not improve simply because someone — or something — says:

“This looks great.”

Sometimes the most valuable response is:

“This argument does not hold up.”

That realization changed the way I use AI.

Instead of asking only for help producing the work, I began asking AI to challenge the work.

Attack the argument.

Find the weakness.

Question the assumption.

Show me what I may have overlooked.

That became one of the most useful parts of my AI-assisted editorial process.

I call it red-teaming.

In this book, I am using that term in an editorial sense: deliberately stress-testing the claims, reasoning, sourcing and framing of a story before publication.

Agreement Is Easy

AI systems are designed to be helpful.

That can become a problem.

If I give an AI system an argument and ask:

“Does this make sense?”

I may receive a supportive response explaining why the argument works.

If I ask:

“Is this a strong article?”

I may hear that the article is thoughtful, compelling or well structured.

That may feel good.

It may also tell me very little.

The problem is not that positive feedback is always wrong.

The problem is that agreement does not test the work.

Journalism needs resistance.

A source may challenge the premise.

An editor may question the evidence.

A reader may notice an assumption the writer missed.

If I want the article to survive those challenges after publication, it makes sense to expose it to some resistance before publication.

AI can sometimes help simulate that kind of critique.

It is not the same as an experienced editor or a knowledgeable subject-matter expert.

But it can provide another angle from which to examine the work.

Ask the Opposite Question

One of the simplest changes I made was changing the way I ask AI for feedback.

Instead of:

“Is this argument strong?”

I can ask:

“What is the strongest evidence-based challenge to this argument?”

Instead of:

“Does this article make sense?”

I can ask:

“Where could a skeptical reader say this article fails?”

Instead of:

“Is this ready to publish?”

I can ask:

“What weakness could justify holding this story?”

The difference is significant.

The first set of questions invites approval.

The second invites resistance.

That resistance can expose problems I might not notice because I am already too close to the work.

Writers Become Attached to Their Arguments

This is not an AI problem.

It is a human problem.

Once I have spent time researching and writing something, I naturally begin to understand the story through the structure I created.

I know what I meant.

I know why I included a particular detail.

I know how the argument developed.

That familiarity can create blind spots.

A paragraph may seem clear to me because I already know the background.

A conclusion may feel obvious because I have been thinking about it for hours.

A source may seem convincing because it supports the direction the story has already taken.

That is exactly when another perspective becomes useful.

Editors have always served that role.

Good editors ask the question the writer may not want to hear.

Why?

How do you know?

Where is the evidence?

Is that really what the source said?

Are you assuming too much?

What might an informed critic object to?

AI can sometimes help simulate that resistance.

Not replace the editor.

Not replace the journalist.

But add another layer of challenge before publication.

What Red-Teaming Means in My Workflow

When I red-team an article, I am not simply asking AI to proofread it.

Proofreading looks for problems in grammar, spelling and presentation.

Red-teaming asks whether the underlying journalism survives criticism.

The questions are different.

What is the weakest claim?

Where is the evidence thin?

Which sentence sounds more certain than the reporting supports?

What assumption am I making?

Is there another plausible interpretation?

What evidence-based weakness might a knowledgeable reader identify?

Have I confused correlation with causation?

Am I treating an opinion as a fact?

Does the headline promise more than the article proves?

Is there missing context that would materially change the reader’s understanding?

Those questions force the work into a more uncomfortable place.

That is the point.

Do Not Manufacture an Opposing Side

There is a danger in telling AI simply:

“Argue the other side.”

The system will usually try.

But the existence of a counterargument does not make the counterargument credible.

It may create a false equivalence.

It may elevate a fringe objection.

It may invent controversy where the evidence is actually quite strong.

That is why I prefer a narrower instruction.

Do not merely give me an opposing opinion.

Show me “evidence-based weaknesses, missing context, unsupported inferences and plausible alternative interpretations.”

That is a much better editorial test.

The question is not:

“Can somebody disagree with this?”

Someone almost always can.

The better question is:

“Does the disagreement expose a legitimate weakness in the evidence or reasoning?”

AI Can Be Wrong About the Weakness Too

There is another important warning.

Red-teaming does not mean accepting every criticism AI produces.

AI can identify a problem that is not actually a problem.

It can misunderstand the argument.

It can invent a counterargument that has little connection to the evidence.

It can overcorrect.

It can treat a well-supported conclusion as questionable simply because I instructed it to find something wrong.

That means the red-team response has to be evaluated too.

This connects directly back to the earlier chapters.

The human remains responsible.

AI output is not evidence.

The human has to exercise judgment.

Red-teaming gives me another perspective.

It does not give AI veto power over the article.

The Goal Is Not to Destroy the Story

A red-team process can go too far.

If I challenge every sentence endlessly, nothing will ever be published.

Every story has limitations.

Every argument can be questioned.

Every source can be criticized.

The goal is not to produce journalism that no human being could possibly challenge.

That is impossible.

The goal is to discover weaknesses that matter.

A missing comma is not the same as a missing source.

A stylistic disagreement is not the same as an unsupported accusation.

A theoretical alternative explanation is not automatically as credible as the explanation supported by the available evidence.

Red-teaming is useful only if the journalist can distinguish criticism generated for the sake of criticism from a material weakness.

Focus on What Could Change the Story

AI can produce long lists.

That does not mean every item deserves equal attention.

If a red-team review gives me ten objections, I do not automatically rewrite the story ten times.

I want to know:

Which objection could change the factual conclusion?

Which one exposes weak sourcing?

Which one reveals missing context or distorted framing?

Which one could damage trust if I ignore it?

That is a more useful filter.

One serious weakness is worth more than ten superficial criticisms.

AI can generate objections.

The journalist has to rank them.

Surviving a Red-Team Pass Does Not Prove the Story Is Correct

This distinction matters.

If a story survives an AI red-team review, that does not certify the journalism.

The AI may have missed something.

It may share the same assumptions that influenced the original work.

Its critique may simply be weak.

Passing one adversarial review means only that **one additional layer of challenge did not reveal a material problem**.

That is useful.

It is not proof.

Verification still matters.

Human editing still matters.

The underlying reporting still matters.

Red-teaming is another safeguard.

It is not a replacement for the others.

The Same AI Is Not an Independent Editor

There is another limitation worth acknowledging.

Sometimes the same AI system that helped with the draft also performs the red-team review.

That can still be useful.

But it is not independent review.

The model may carry forward assumptions from the earlier discussion.

It may understand the article through the framing already established in the conversation.

It may reproduce the same blind spots.

The higher the stakes, the less comfortable I should be relying on one system to create the work and then declare that it survived criticism.

Outside human review may be necessary.

Additional sourcing may be necessary.

A different evaluation approach may be necessary.

The AI red team is one perspective.

It should not pretend to be every perspective.

Red-Teaming Can Improve Reporting, Not Just Writing

One of the most useful things about the process is that it can send me back to the reporting.

Maybe the problem cannot be fixed by rewriting a sentence.

Maybe I need another source.

Maybe I need the original document.

Maybe I need to check the timeline again.

Maybe I need to separate what is confirmed from what I believe happened.

That is when red-teaming becomes more than an editing exercise.

It becomes part of the reporting process.

A good challenge can reveal that the story is not finished yet.

And that is valuable information to receive before publication.

Challenge the Headline Too

Headlines deserve their own red-team review.

A headline can be technically related to the article and still overstate what the reporting establishes.

That is especially tempting in digital publishing.

Strong language attracts attention.

Certainty attracts clicks.

Conflict attracts attention.

But a headline is still part of the journalism.

If the headline is stronger than the evidence, the article begins with a credibility problem.

So one of the questions worth asking is:

“Does the headline make a claim the article cannot fully support?”

That simple test can prevent a lot of unnecessary trouble.

Red-Team the AI Too

There is another layer to this process.

The AI itself should be challenged.

If AI summarizes a source, I can ask:

What did you omit?

What uncertainty did you flatten?

Show me where the source supports that statement.

What alternative interpretation exists?

If AI suggests a conclusion, I can ask:

“What evidence would make this conclusion wrong?”

If AI gives me a confident answer, I can ask:

“What part of this answer requires the most verification?”

The goal is not to create an endless conversation with the machine.

The goal is to prevent confidence from becoming authority.

AI should not merely challenge my work.

I should challenge its work too.

A Strong Review Also Identifies What Survives

Red-teaming should not become an exercise in finding fault for its own sake.

A useful review should also identify which claims remain strong after scrutiny.

What is well supported?

Which conclusion survived the challenge?

Which source still holds up?

Which section does not need to be rewritten?

That matters because the purpose of red-teaming is diagnosis.

Not destruction.

A good review separates the parts of the story that need more work from the parts that have already earned their place.

The Psychological Value of an Adversarial Partner

There is another benefit to red-teaming that is harder to measure.

It makes criticism normal.

Instead of treating criticism as something that arrives after publication, I can make it part of the production process.

That changes my relationship with the draft.

The goal becomes less about defending what I wrote and more about improving it.

If the red team finds something important, good.

Better now than after publication.

If the argument survives, good.

I have more confidence in the process because I tried to break it.

Not because the red-team pass proved the story correct.

It did not.

But because the work has faced another layer of scrutiny.

A Workflow for Challenging the Work

A journalist does not need an elaborate system to begin.

A simple editorial red-team workflow can look like this:

Finish the draft.

Identify the central claim.

Ask for the strongest evidence-based challenges.

Look for weak or overstated claims, missing context and unsupported inferences.

Identify which weaknesses could materially change the story.

Then evaluate every criticism yourself.

Some will be useful.

Some will be irrelevant.

Some will be wrong.

The human decides which ones require action.

That may lead to a rewrite.

It may lead to more reporting.

It may lead to stronger sourcing.

Or it may confirm that the original argument already has strong support.

All of those outcomes can be useful.

Challenge Before the Audience Does

Every published story eventually meets readers who did not participate in creating it.

They bring different experiences.

Different knowledge.

Different assumptions.

Different questions.

Some will notice things the writer missed.

That cannot be eliminated.

But journalism can become stronger when the writer deliberately invites challenge before publication.

AI gives me another way to do that.

Not because AI knows better than the journalist.

Not because its criticism is automatically correct.

And not because surviving an AI challenge proves the journalism is right.

The value comes from resistance.

Do not use AI only to help build the argument.

Use it to pressure-test the argument too.

Then decide what survives.

Because a story that has been seriously challenged before publication has a better chance of surviving the challenges that come after it.


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

From Doing Everything Myself to Directing the Workflow

By Cheval John | Vallano Media
This article was created with the assistance of artificial intelligence.
The final version was reviewed, edited and fact-checked by the author


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

For most of my career, writing meant doing nearly everything myself.

Research the story.

Find the sources.

Take the notes.

Organize the information.

Write the draft.

Rewrite the draft.

Check the facts.

Edit the copy.

Come up with the headline.

Prepare the article for publication.

Then start all over again with the next story.

That process was familiar because it was the way I had always worked.

It was also exhausting.

Journalists often wear several hats, especially when they work independently or in smaller organizations.

A reporter may also become the researcher, editor, publisher, social-media producer and, depending on the project, even the person creating graphics.

For a long time, I simply accepted that as part of the job.

Then artificial intelligence changed the way I thought about the work.

Not because AI could suddenly do everything for me.

It could not.

What changed was that I began to realize I no longer had to perform every part of the process in exactly the same way.

I could direct the workflow.

That was a much bigger change than simply learning how to use a chatbot.

The First Stage: Asking Questions

My early use of artificial intelligence was not sophisticated.

Like many people, I started by asking questions.

I treated AI almost like a conversational search tool.

Ask something.

Get an answer.

Ask another question.

Move on.

There was nothing particularly strategic about it.

At that point, I was using AI.

I was not yet working with AI.

That distinction would become important.

The real change began when I stopped thinking only about individual questions and started thinking about the entire process.

What happens before I write?

What happens after I write?

Where do mistakes usually occur?

Which parts take the most time?

Which parts require judgment?

Which parts are repetitive?

Which parts could benefit from another set of eyes?

Once I began thinking that way, AI stopped being only a question-and-answer tool and started becoming part of a workflow.

The Work Did Not Disappear

It is easy to describe AI as a labor-saving technology.

Sometimes it is.

But that description can be misleading.

The work did not disappear.

The work changed.

Instead of spending all of my time manually performing every task, I increasingly spent time deciding what needed to happen, what AI could assist with and what still required my direct attention.

That sounds subtle.

It is not.

Consider research.

A traditional workflow might involve opening a series of tabs, reading articles, taking notes and trying to identify connections manually.

An AI-assisted workflow might help organize documents, compare information or identify questions more quickly.

But somebody still has to decide which sources are trustworthy.

Somebody still has to notice when important context is missing.

Somebody still has to recognize when two sources appear to contradict each other.

And somebody still has to decide what belongs in the final story.

That person is still me.

AI can reduce some forms of manual work while creating another responsibility: supervision.

From Doing Everything to Directing the Workflow

This is the part I did not understand when I first started using AI.

I thought the main benefit would be speed.

Write faster.

Research faster.

Edit faster.

Those benefits are real.

But the deeper change has been learning how to direct the work.

The shift was not from working to supervising.

It was from performing every task manually to deciding which tasks I should still perform, which AI could assist with and where human approval had to remain.

One workflow may be focused on research.

Another may challenge the argument.

Another may examine factual claims.

Another may help transform a completed article into a different format.

Another may help evaluate whether the final product still sounds like me.

Some of those workflows are simple and manually triggered.

Others are more structured.

Not every useful AI workflow needs to be autonomous.

The point is not to remove the human from the process.

The point is to build a process where the human knows when to step in.

I Did Not Start With a Master Plan

The strange part is that this happened gradually.

I did not sit down one morning and announce that I was going to build a collection of AI-assisted workflows.

Much of it came from trial and error.

I encountered a problem.

I tried something.

Sometimes it worked.

Sometimes it did not.

I needed a better way to verify information.

A workflow developed.

I needed a way to challenge weak arguments.

Another workflow developed.

I needed to repurpose an article without losing its meaning.

Another process emerged.

Some workflows worked immediately.

Others had to be changed.

Some became more useful after repeated use.

Some probably were not worth keeping.

Over time, those individual solutions began to form a system.

That is when I started realizing that I was no longer simply using AI.

I was designing ways to work with it.

The Journalist Becomes the Editor of the Output

Traditional journalism has always involved editing.

The difference now is that the journalist may also have to edit what the machine produces.

That means more than correcting grammar.

It means questioning assumptions.

Rejecting weak suggestions.

Checking sources.

Restructuring an answer.

Recognizing when the system has misunderstood the assignment.

Sometimes the most important thing I do is tell the AI:

No.

That is wrong.

That is unsupported.

That does not sound like me.

That is not the question I asked.

Try again.

Those moments matter because they reveal something that gets lost when AI is described as automatic.

The process is often interactive.

The final result may emerge from several rounds of challenge, correction and refinement.

That makes the human role different from traditional writing, but not less important.

In some situations, it can become more demanding because the journalist must supervise both the journalism and the AI-assisted process.

Direction Requires Knowing What Good Looks Like

There is another problem with telling people to simply “use AI.”

You have to know what you are trying to produce.

AI cannot compensate for having no standards.

If I do not know what a strong news story looks like, I cannot reliably judge whether AI has helped create one.

If I do not understand verification, I may not recognize an unsupported claim.

If I do not understand my own voice, I may allow AI to replace it with generic language.

Delegation only works if the journalist still understands the task well enough to judge the result.

That matters because over-delegation carries its own risk.

If journalists stop practicing the underlying skills of research, verification, writing and editing, they may become less capable of recognizing when AI has produced weak work.

AI can increase capability.

It does not automatically provide judgment.

The better I understand journalism, the better I can direct AI inside a journalistic workflow.

A Different Kind of Productivity

Before I began using AI seriously, productivity often meant working harder or working longer.

There were only so many hours available.

If an article took three hours, producing another article often meant finding another three hours.

AI changes that equation, but not as simply as the hype sometimes suggests.

The goal is not to produce as much content as possible.

The goal is to use saved time intelligently.

The most useful question is not:

“How much faster can AI make me?”

It is:

“What should I do with the time AI gives back?”

If AI helps reduce the mechanical parts of a task, I can spend more time checking the work.

I can challenge the argument.

I can examine another source.

I can rethink the headline.

I can decide that a story is not ready.

That is a much healthier definition of productivity than simply publishing more.

Speed only matters if the quality survives.

When the Workflow Fails

Directing AI-assisted work also means accepting that the workflow will sometimes fail.

AI may misunderstand the task.

It may give me information that looks useful but is not.

It may repeat itself.

It may introduce language that sounds polished but weakens the point.

It may send research in the wrong direction.

Those moments are not exceptions to the process.

They are part of the process.

The important questions are simple:

Did I catch the problem?

Do I understand why it happened?

Do I need to change the workflow?

That is how the system improves.

Not because AI becomes perfect.

Because the human process around it becomes better.

Building the System While Using It

One of the unusual things about my experience is that I built many of these workflows before I knew what to call them.

I was solving problems.

I was creating repeatable steps.

I was assigning specific roles to AI.

I was deciding where human approval had to remain.

Only later did I realize that what I had been building resembled structured AI workflows and, in some cases, agent-like systems.

Most of those systems were not fully autonomous.

They were usually manually triggered and specialized.

That distinction matters.

Not every useful AI workflow needs to operate independently.

Sometimes the value comes from building a repeatable process that helps the human work more consistently.

I had not learned the terminology first and then applied it.

I developed the practice first and learned the terminology afterward.

That may be one reason the systems felt natural.

They were built around real problems rather than abstract concepts.

The Managerial Shift

This change also affected how I thought about my role inside Vallano Media.

I was no longer simply writing articles.

I was increasingly managing a publishing system.

Research needed direction.

Verification needed standards.

Drafting needed oversight.

Graphics needed review.

Publishing needed coordination.

AI could assist with many of those functions, but I remained the person deciding how the pieces fit together.

That is where the shift from writer to director became clear.

The word “director” does not mean standing above the work.

It means coordinating it.

The work still has to be understood.

The standards still have to be maintained.

The final decision still has to be made.

But I no longer have to perform every task manually in order to remain in control.

What Other Journalists Can Learn From This

The lesson is not that every journalist needs dozens of workflows.

The lesson is simpler.

Start by examining the work you already do.

Where do you spend the most time?

Where do mistakes occur?

Which tasks are repetitive?

Which tasks require judgment?

Which tasks could be assisted without handing away editorial control?

Then test one small process.

Do not automate the entire newsroom.

Do not start with the highest-risk task.

Pick something manageable.

Maybe it is organizing notes.

Maybe it is generating questions to consider.

Maybe it is comparing two versions of a draft.

Maybe it is asking AI to challenge an argument before publication.

Then examine what happened.

Did it help?

Did it save time?

Did it introduce problems?

What still required human judgment?

That is how a workflow begins.

The Work Is Still Mine

AI has changed how I work.

It has not changed who is responsible for the work.

That was the lesson of Chapter 1.

Chapter 2 adds another layer.

Responsibility does not require doing everything manually.

Control does not mean refusing assistance.

The journalist can delegate parts of the process without delegating accountability.

That is the shift I am still learning to make.

From doing every task myself to directing a workflow.

From asking AI isolated questions to designing repeatable processes.

From thinking only like a writer to thinking more like an editor, manager and publisher.

The technology did not remove me from the process.

It changed where I add the most value.

And increasingly, that value comes from knowing what to direct, what to question, what to verify and when to say no.


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

The Journalist Is Still Responsible

By Cheval John | Vallano Media
This article was created with the assistance of artificial intelligence.
The final version was reviewed, edited and fact-checked by the author


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.

Artificial intelligence can help a journalist work faster.

It can organize information, summarize documents, compare sources, identify gaps in an argument, suggest questions, assist with editing and challenge assumptions the journalist may have overlooked.

But there is one thing it cannot do.

It cannot take responsibility for the journalism.

That responsibility remains human.

The journalist remains responsible for the work they produce.

Editors remain responsible for the decisions they make.

News organizations remain responsible for the systems they approve, the standards they set and the safeguards they require.

AI can become part of the process without becoming accountable for the result.

That distinction sounds simple.

In practice, it is not.

If an AI system produces a paragraph that eventually appears in an article and that paragraph contains an error, who is responsible?

If AI summarizes a document incorrectly and nobody catches it, who owns the mistake?

If a newsroom introduces an AI tool into its workflow without adequate safeguards, can responsibility simply be pushed down to the individual journalist?

These questions become more important as AI systems move deeper into journalism.

The answer cannot be that the technology is responsible.

Accountability still belongs to the people and organizations using it.

The Temptation of Speed

One of the most attractive things about artificial intelligence is speed.

Tasks that once required substantial manual work can sometimes be completed much faster with AI assistance.

Information can be organized quickly.

Long documents can be examined.

Ideas can be compared.

A first draft can take shape faster than it might have before.

For journalists working under deadlines, that can be incredibly useful.

But speed can create another danger.

The faster information appears, the easier it can become to accept it without examining it closely.

A polished answer can feel authoritative even when the underlying information is incomplete, misleading or wrong.

And an AI system does not have to invent a fact to cause problems.

It can omit crucial context.

It can emphasize the wrong detail.

It can flatten uncertainty.

It can steer attention toward one interpretation while neglecting another.

That is why human judgment becomes more important, not less.

AI does not eliminate the need for verification.

It increases the importance of knowing what needs to be verified and why.

Polished Does Not Mean Correct

One of the first lessons anyone working seriously with generative AI learns is that confident language does not guarantee accurate information.

An AI system can produce an answer that sounds professional, complete and perfectly reasonable.

It can also be wrong.

That creates a particular problem for journalism because credibility depends on the accuracy of what gets published.

A spelling mistake can be embarrassing.

A factual mistake can damage trust.

An unsupported accusation can create much more serious consequences.

The danger is not simply that AI makes mistakes.

Human beings make mistakes too.

The difference is that generative AI can produce those mistakes quickly and present them in language that already looks finished.

That means journalists cannot judge AI output by how polished it appears.

They have to judge it by the evidence behind it.

AI Output Is Not Evidence

This is one of the rules I have increasingly adopted in my own work: AI output is not evidence.

If an AI system tells me something happened, that does not make the statement true.

If it provides a date, statistic, historical claim or quotation, that information still has to be traced back to reliable evidence.

AI can help point me toward something worth investigating.

It can help organize what I find.

It can help compare multiple pieces of information.

But an AI-generated claim should never be treated as verified simply because the system produced it.

That distinction has changed the way I work.

Instead of asking only, “What is the answer?” I increasingly ask:

“What evidence supports the answer?”

Those are very different questions.

The first can produce information.

The second begins the verification process.

Human Oversight Has to Mean Something

There is a phrase that appears constantly in discussions about artificial intelligence:

Human in the loop.

It sounds reassuring.

But simply putting a human somewhere in the workflow does not automatically make the process responsible.

A journalist can still accept an AI-generated summary without checking it.

An editor can still approve a story too quickly.

A newsroom can still adopt an AI system without understanding its limitations.

Human oversight only works when the human is actually verifying, questioning and exercising judgment.

Otherwise, the human becomes little more than a rubber stamp.

The goal should not simply be to keep a person somewhere in the process.

The goal should be to make sure that person still has the time, authority and responsibility to challenge what the technology produces.

The Human Has to Push Back

Another lesson I have learned is that AI becomes more useful when I stop treating it as something that should agree with me.

If I present an argument and ask an AI system whether it is good, I may receive a helpful answer.

But I often learn more by asking it to attack the argument.

What am I missing?

What assumptions am I making?

What would a skeptical reader challenge?

What evidence would weaken my conclusion?

What alternative explanation should I consider?

That is where AI can become useful as an adversarial partner rather than simply a writing assistant.

But there is another layer to this.

The AI’s criticism also has to be challenged.

It can identify a weakness that does not actually exist.

It can suggest an alternative interpretation that is unsupported.

It can overcorrect.

So the journalist has to evaluate both the original argument and the AI’s response to it.

The human remains responsible for deciding what survives.

AI Is Not Just Another Spellcheck

Journalists have always used technology.

Search engines changed research.

Digital recorders changed interviews.

Transcription software changed note-taking.

Content-management systems changed publishing.

Spellcheck changed editing.

So why should generative AI be treated differently?

The difference is not that AI is the first technology journalists have ever used.

It is that generative AI can produce outputs that resemble reasoning, interpretation and writing.

It does not merely correct a misspelled word.

It can suggest an argument.

It can summarize a document.

It can rewrite a paragraph.

It can compare competing explanations.

It can recommend what information appears most important.

That gives it greater potential to influence editorial judgment.

And the closer technology moves toward those judgment-heavy parts of journalism, the more carefully journalists need to understand what the system is doing.

Judgment Cannot Be Automated Away

Journalism is filled with decisions that go beyond arranging facts.

Which facts matter most?

Which source is credible?

Which detail belongs near the top of the story?

Which claim requires additional verification?

When is there enough evidence to publish?

When should publication wait?

What context does the audience need?

Those decisions involve judgment.

AI may help inform that judgment, but it cannot remove human responsibility for the decision.

That becomes especially important when a story involves uncertainty.

Real reporting is rarely as clean as the completed article makes it appear.

Sources may disagree.

Documents may be incomplete.

Eyewitness accounts may conflict.

Statistics may require context.

People may have incentives to describe the same event differently.

A journalist has to work through those contradictions and decide what can responsibly be said.

AI can assist with that process.

It cannot own the decision.

Responsibility Is Bigger Than a Byline

I often think about this in very simple terms.

If my name appears on an article, I am responsible for what is in it.

But responsibility in journalism extends beyond the byline.

Editors, producers, researchers and others may shape journalism without their names appearing prominently on the final product.

Whether my name appears on the work or I contribute behind the scenes, I am still responsible for the decisions I make in producing it.

And organizations have responsibilities too.

A newsroom cannot introduce AI tools, encourage their use and then pretend every consequence belongs only to the reporter.

Management decisions matter.

Training matters.

Editorial standards matter.

The design of the workflow matters.

Responsibility is shared, but it does not disappear.

What That Means for This Book

Artificial intelligence will play a significant role in the creation of this book.

It will help me organize research.

It will challenge arguments.

It will help examine drafts.

It may suggest language that ultimately survives into the finished manuscript.

But it will not receive editorial authority over the work.

I will decide what stays.

I will decide what goes.

I will decide whether the argument reflects the evidence.

And I will be responsible for what is published.

If an AI system produces something inaccurate, misleading, unsupported or simply not good enough, I cannot defend the final result by saying:

“The AI told me.”

That is not an editorial defense.

A Different Kind of Partnership

None of this makes AI unimportant.

Quite the opposite.

Used carefully, it can become one of the most useful tools available to a modern journalist.

But the most productive relationship may not be one in which the journalist asks AI to do the thinking.

It may be one in which AI helps the journalist think harder.

Challenge this.

Compare these sources.

Find the weakness.

Show me another interpretation.

What am I overlooking?

Where does this argument fail?

Those kinds of questions turn AI from a shortcut into something closer to an intellectual sparring partner.

And that may ultimately be one of its most valuable roles in journalism.

Responsibility Remains Human

The tools journalists use have always changed.

The responsibilities underneath the profession have changed much less.

Verify the information.

Understand the evidence.

Provide context.

Be fair to the people involved.

Correct mistakes.

Do not publish something simply because it sounds convincing.

Artificial intelligence does not erase those responsibilities.

It makes them more visible.

The journalist may have a new assistant.

The newsroom may have faster tools.

The organization may be able to accomplish more in less time.

But when journalism reaches the public and someone asks, “Can I trust this?” the answer cannot be:

“The AI said it was right.”

The answer has to come from the work behind the story.

And responsibility for that work remains human.


Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.