The AI Editorial Prompt Chain: How the Reporting Conversation Actually Worked
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.
There Was No Magic Prompt
The FIFA reporting did not come from a single master instruction.
One question produced research. Research produced another question.
Verification exposed gaps.
Those gaps required more sourcing.
Analysis produced possible conclusions.
Those conclusions were challenged.
As that pattern became more recognizable, Vallano Media coined the name “AI Editorial Prompt Chain” to describe its own workflow.
The term refers to the recurring sequence of questions, research actions, verification steps and editorial decisions that developed through Vallano Media’s AI-assisted reporting work.
The name came after the process had already begun to emerge through use.
It was not a formal system designed before the reporting started.
And the name should not be confused with a claim that Vallano Media invented the underlying practices.
Research, sourcing, verification, fact-checking, editing, professional judgment and adversarial editorial review are established practices.
Vallano Media’s contribution was to organize those practices within its own AI-assisted process and give that recurring structure a name: the AI Editorial Prompt Chain.
Not every stage was literally a prompt.
Some were research actions.
Some were source checks.
Others were editorial decisions.
The value was in how those pieces worked together.
The Prompt Chain Began With a Question, Not an Assignment to Write
The project did not begin with: “Write me an article about FIFA.”
It began with questions.
What was being proposed?
Who supported it?
Who opposed it?
What was confirmed?
What remained uncertain?
That distinction matters.
If the first instruction is simply to produce an article, the system begins filling the page.
If the first instruction is to help investigate a question, the workflow begins somewhere very different.
Research Prompts Created More Questions
AI was useful for helping map the information environment surrounding the story.
That included:
– official statements;
– independent reporting;
– relevant organizations and stakeholders;
– chronology;
– competing claims;
– apparent contradictions;
– and unanswered questions.
But the process did not move neatly from research to writing.
A source could introduce another organization.
A statement could raise a new timing question.
Two apparently contradictory claims could become compatible once their dates were examined.
One answer often created the next question.
That was the chain.
Verification Changed the Conversation
Eventually the questions changed.
Instead of only asking: What does the evidence say?
The workflow began asking: Is this actually verified?
What evidence supports this?
Is there an original source?
Is independent confirmation available?
What remains uncertain?
Could the wording be stronger than the evidence?
AI could help identify the claims that required verification.
But AI could not become its own evidence.
The underlying sources still had to perform that job.
Analysis Came After the Evidence
Only after the research foundation became stronger did the conversation move toward interpretation.
What did the developments mean?
What alternative explanation could fit the same facts?
Which conclusions were supported by the evidence?
Which went beyond it?
The process increasingly resembled a loop:
Evidence → Analysis → Challenge → Verification → Revised Analysis
That loop could move backward at any time.
Verification could expose a weakness.
A weakness could require more research.
Additional research could change the analysis.
That was not inefficiency.
That was the workflow doing its job.
The Prompt Chain Became Adversarial
AI became particularly useful when it was no longer asked simply to help strengthen the article.
It was asked to challenge it.
What is wrong with this argument?
Where is the evidence weakest?
What assumption has not been demonstrated?
What would a skeptical editor challenge?
Are we confusing chronology with causation?
Is an important perspective missing?
Sometimes the most useful AI response created additional work.
That was useful because the objective was not to generate an article as quickly as possible.
The objective was to produce something Vallano Media was willing to publish.
The Outline Was an Editorial Proposal
AI could help organize the growing body of verified material.
It could suggest:
– which information should appear first;
– where background belonged;
– which sections repeated one another;
– whether a section depended on information appearing too late;
– and whether the reporting supported more than one article.
But an AI-generated outline remained a proposal.
The journalist decided the architecture.
That distinction became especially important when the FIFA reporting developed into a two-part series rather than one oversized article.
Drafting Was Iterative, Not Automatic
By the time drafting began, the project already had:
– an editorial objective;
– a source base;
– verified claims;
– a working chronology;
– an analytical direction;
– and an outline.
AI was therefore not being asked to invent the journalism.
It was assisting with the expression and organization of reporting that already existed.
And even then, the first draft was only another stage.
Passages could be rewritten.
Claims could be weakened.
Sections could be removed.
New questions could send the work back to research.
Human Review Was Present Throughout
The process was never: AI does the work → human checks it at the end.
Human judgment appeared throughout the workflow.
The journalist selected the story.
The journalist evaluated sources.
The journalist determined which questions mattered.
The journalist decided whether the evidence supported a conclusion.
The journalist accepted or rejected AI suggestions.
And the journalist made the final publication decision.
AI participation could be extensive without AI authority becoming extensive.
Completeness Became a Separate Question
Fact-checking asks whether something is wrong.
But a story can contain no obvious factual error and still be incomplete.
An important stakeholder may be missing.
A relevant piece of chronology may have been overlooked.
The strongest counterargument may not have been represented.
That led to a separate completeness audit.
The question was no longer simply: Is everything here correct?
It also became: Is something important missing?
Authentic Voice and Thought Flow
Another stage emerged as AI-assisted drafting became more common.
Vallano Media began using what it calls an Authentic Voice and Thought-Flow Review.
This is Vallano Media’s own terminology rather than an established industry standard.
The review asks whether AI assistance has:
– made the writing unnecessarily generic;
– removed useful qualification;
– flattened the natural reasoning;
– created transitions the writer would not naturally use;
– or made the finished article sound more like generated prose than journalism.
Correct information is not automatically good writing.
The finished work still has to sound like the publication responsible for it.
Final Approval Could Not Be Automated
Eventually, no additional AI question could make the final decision.
Someone still had to decide: Is the reporting sufficiently verified?
Is the language fair?
Does the evidence support the headline?
Are the qualifications preserved?
Is anything important missing?
Does this actually need to be published?
And finally: Is Vallano Media willing to put its name on it?
That decision remained human.
The Chain Was Never Really a Straight Line
The simplest version of the process can be written as:
Story Idea → Research → Source Evaluation → Verification → Analysis → Additional Research → Outline → Draft → Human Review → Editorial Red Team → Completeness Audit → Authentic Voice and Thought-Flow Review → Fact Check → Final Approval → Publication → Repurposing / Follow-Up
“AI Editorial Prompt Chain” is Vallano Media’s name for this specific workflow structure.
It describes how the company organized a recurring set of editorial practices around AI-assisted reporting; it does not claim that the individual journalistic practices themselves originated with Vallano Media.
And the real workflow contained loops.
Verification could return the project to research.
Red-team review could return it to analysis.
Fact-checking could return it to drafting.
Post-publication developments could reopen the reporting.
The intelligence of the workflow came partly from changing the question as the work changed.
A strong sequence of questions can improve the conversation with AI.
A strong editorial workflow determines whether the result is usable.
The White Paper Series Continues Next Week
The Vallano Media white paper series continues next week with Chapter 8: “From Research to Publication: Why the FIFA Reporting Became a Two-Part Series.”
Chapter 8 examines why the reporting ultimately required two separate articles, how the structure emerged from the research rather than being predetermined, and why the distinction between establishing what happened and analyzing what it could mean became important to the final journalism.
Future chapters will examine graphics and distribution, editorial restraint, post-publication developments, and the complete Vallano Media AI-Assisted Journalism Framework.
The series will also introduce practical resources developed through the project, including the Vallano Media Verification Checklist, Source Hierarchy, Editorial Red-Team Checklist and AI Disclosure Standard.

Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.
Scaling Without Losing Control
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.
Eventually, the question changes.
At first, I was trying to figure out how to use AI responsibly.
Then I was trying to build a workflow I could trust.
Then I wanted to make that workflow repeatable.
Then measurable.
But once a system starts working, another question appears:
“What happens when I try to do more with it?”
More stories.
More platforms.
More research.
More graphics.
More automation.
More clients.
More coverage.
More people.
More responsibility.
That is where scaling begins.
And that is where control can start to slip.
Growth Creates a New Kind of Risk
A workflow that works for one article does not automatically work for ten.
A process that works when I am personally watching every step may not work the same way when tasks are automated, delegated, or running at the same time.
Growth changes the system.
That matters.
The danger is not only that the work becomes larger.
The danger is that the distance between the decision and the result becomes larger too.
When I am doing everything myself, I can see almost every handoff.
When the system grows, some of those handoffs become harder to see.
That is where mistakes can hide.
Scale Is Not the Goal
There is an assumption underneath a lot of technology conversations that bigger is better.
More output.
More automation.
More users.
More clients.
More reach.
But not everything worth doing needs to be scaled.
Some work is valuable precisely because it remains slow, deliberate, or highly personal.
Some reporting deserves hours of attention.
Some investigations should resist automation.
Some projects may never become efficient in the traditional sense.
That does not make them failures.
So I do not want to scale for the sake of scaling.
The goal is “responsible capacity”.
The ability to do more where doing more actually creates value.
Scaling Is Not Just Doing More
It is easy to think scaling means increasing output.
More articles.
More posts.
More clients.
More revenue.
More automation.
Those things may be part of it.
But real scaling means something more difficult:
“Increasing capacity without losing the standards that made the system valuable in the first place.”
If I double the output and double the errors, I have not scaled well.
If I automate more tasks but lose visibility into how decisions are being made, I have not improved the system.
If I grow faster than I can verify, review, or understand the work, I have created a larger problem.
Scale should expand capacity.
Not expand confusion.
And scale should never become the excuse for producing more work that matters less.
The Workflow Has to Grow With the Work
A small workflow can survive informality.
I can remember what I did.
I can keep notes in my head.
I can recognize which version is final.
I can remember which source I trusted.
That becomes harder as the volume grows.
So the workflow has to become more explicit.
Not necessarily more complicated.
More explicit.
What happens first?
What gets verified?
What requires human approval?
What can be automated?
What cannot?
Where does the work stop if something goes wrong?
Who owns the final decision?
Those questions become more important as the system grows.
More AI Means More Oversight, Not Less
This may sound backwards.
AI can reduce the amount of manual work I have to do.
But greater AI integration can increase the importance of oversight.
Why?
Because more tasks can happen faster.
More output can move through the system.
More mistakes can move with it.
A bad assumption inside one manual task may affect one piece of work.
A bad assumption inside an automated process can be repeated across many outputs.
That means the cost of a weak checkpoint can increase as the workflow expands.
Automation changes the scale of both success and failure.
The Human Role Changes Again
Earlier in this book, I wrote about the human in the workflow.
At small scale, that might mean reviewing a draft.
Checking a source.
Approving a graphic.
Choosing a headline.
At larger scale, the human role becomes more about designing and supervising the system itself.
What tasks should AI handle?
What should remain manual?
Which decisions require approval?
What warning signs should stop the process?
What happens when something fails?
How much work can I realistically review?
That is a different kind of responsibility.
The human is no longer only editing the output.
The human is managing the conditions under which the output is produced.
But there is an important limit.
“Human oversight does not scale simply by adding more work to the same human.”
Eventually, the system has to account for the limits of human attention too.
Control Has to Be Designed In
I do not want control to depend on me noticing that something feels wrong.
That works sometimes.
It does not scale.
Control has to be part of the workflow.
That means checkpoints.
Verification.
Clear approval stages.
Version control.
Documented standards.
Fallback procedures.
Visible automation.
The ability to stop the process.
But there is another trap here.
A system can look controlled on paper and still fail in practice.
A dashboard is not control.
A checklist is not control.
An approval button is not control.
Those things matter only if they change what happens when something goes wrong.
The goal is not the appearance of oversight.
It is functioning oversight.
Automation Should Have Boundaries
One of the easiest mistakes is to automate something simply because it can be automated.
That is not enough.
The better question is:
“Should this task be automated?”
Some tasks are good candidates.
Repetitive monitoring.
Formatting.
Organizing information.
Routine reminders.
Basic transformations.
Some tasks require more caution.
Source evaluation.
Interpretation.
Final publication decisions.
High-risk factual claims.
Anything where context matters more than speed.
The boundary should not be based only on technical capability.
It should be based on consequence.
Agents Make This Even More Important
Depending on how they are designed, AI agents can monitor information, trigger actions, move information between steps, prepare material, and perform recurring tasks.
That can create real capacity.
But agents can also create distance.
A task may run without me actively initiating every step.
That makes visibility important.
I need to know:
What triggered the action?
What information did it use?
What did it produce?
What happens if it is wrong?
Can I stop it?
Can I review what happened?
Can I recover?
An agent should not become a black box simply because it saves time.
There is also another risk:
“autonomy creep.”
A system might begin with an agent monitoring information.
Then it starts summarizing.
Then recommending.
Then triggering another action.
Each expansion can seem small by itself.
Eventually, the agent may be doing far more than the original workflow intended.
That is why boundaries need review.
Authority can expand gradually even when nobody explicitly decided to expand it.
Scale Can Hide Weaknesses
Small systems often reveal their problems quickly.
When I personally touch every part of the workflow, I notice friction.
When the system expands, some problems become less visible.
Maybe an automation works most of the time.
Maybe a prompt slowly starts producing weaker results.
Maybe a source changes its format.
Maybe a workflow depends too heavily on one tool.
Maybe a shortcut becomes normal.
The system can keep producing output while quality quietly declines.
That is why measurement matters.
Chapter 14 was not separate from scaling.
It was preparation for it.
If I do not know how the workflow performs at small scale, I will have a harder time understanding what happens when it grows.
And averages are not enough.
A system can perform well most of the time and still produce one failure serious enough to matter.
Average performance can hide individual failures.
Standardization Helps — Until It Does Not
Scaling usually requires some standardization.
Templates.
Checklists.
Naming systems.
Reusable prompts.
Defined workflows.
Those things make repetition easier.
But there is a limit.
Journalism is not manufacturing.
Stories are different.
Sources are different.
Risks are different.
Some assignments need more reporting.
Some need more verification.
Some need legal review.
Some need speed.
Some need patience.
The workflow should create consistency without forcing every story into the same shape.
A standardized process should make judgment easier to apply.
It should not replace judgment with procedure.
The System Needs Exceptions
A mature workflow needs rules.
It also needs a way to break them deliberately.
Not casually.
Deliberately.
If a story requires more verification, the workflow should allow it.
If an automation fails, I should be able to switch to a manual process.
If a source cannot be confirmed, publication should stop.
If a project does not fit the standard template, I should be able to adapt.
Exceptions are not always signs that a system failed.
Sometimes they are evidence that judgment is still present.
Growth Can Create False Confidence
This is another danger.
A system works repeatedly.
I become comfortable with it.
The output looks good.
The process feels familiar.
That familiarity can turn into confidence.
Then confidence can turn into assumption.
That is when I may stop asking questions.
The workflow worked yesterday.
The source was reliable last time.
The automation usually works.
The AI normally gets this right.
That is how oversight can weaken.
Past performance can justify confidence.
It should not eliminate verification.
Scale Magnifies More Than Errors
A small error repeated once is small.
A small error repeated 100 times is not.
That is one of the biggest differences between manual work and automated work.
A formatting mistake can multiply.
A bad prompt can multiply.
A wrong assumption can multiply.
A weak source can multiply.
A misleading headline pattern can multiply.
But factual mistakes are not the only things that repeat.
Framing can repeat.
Source preferences can repeat.
Assumptions can repeat.
Blind spots can repeat.
Bias can repeat.
The more repeatable the system becomes, the more important it is to make sure the thing being repeated is worth repeating.
Efficiency multiplies whatever is already inside the system.
Good or bad.
Capacity Has a Limit
AI can expand capacity.
It does not eliminate limits.
I still have only so much attention.
So much energy.
So much time.
So much ability to review.
That means there is a point where additional output stops being useful.
If I can generate 20 drafts but only responsibly review five, then 20 drafts are not capacity.
They are backlog.
Scaling has to account for the human bottleneck too.
That may be the most important bottleneck in the entire system.
The Review Capacity Has to Scale Too
If production grows, review capacity has to grow with it.
That could mean:
better tools,
better organization,
stronger checkpoints,
clearer priorities,
fewer unnecessary outputs,
or eventually more people.
But there has to be enough review capacity to match the amount of work flowing through the system.
Otherwise AI simply creates more material than I can responsibly supervise.
That is not scale.
That is overload.
Adding People Changes the Workflow
Eventually, scaling may involve other people.
Editors.
Writers.
Researchers.
Designers.
Clients.
Collaborators.
Adding people can increase capacity.
It also creates more handoffs.
And every handoff creates another place where assumptions can develop.
Who verified this?
Who approved it?
Which version is final?
Who owns the decision?
Was this checked already, or did everyone assume someone else checked it?
Once more people enter the system, the workflow has to become understandable outside my own head.
Other people need to know:
What the standard is.
What AI can be used for.
What needs verification.
What requires approval.
What should be documented.
What happens when there is uncertainty.
What happens when something goes wrong.
A workflow that only makes sense to the person who created it is difficult to scale.
Documentation Becomes Infrastructure
At small scale, documentation can feel optional.
At larger scale, it becomes infrastructure.
Not because every process needs a giant manual.
It does not.
Too much documentation can become its own form of friction.
The goal is to preserve important knowledge.
Not bury the workflow under paperwork.
Useful documentation can preserve:
standards,
decisions,
workflows,
sources,
prompts,
exceptions,
lessons from failures.
It turns individual knowledge into organizational knowledge.
That matters whether the organization has two people or 200.
A Fallback Has to Actually Work
I can say I have a fallback.
That does not mean I do.
If an automation breaks, can I really continue manually?
If a tool disappears, do I know another way to perform the task?
If a source feed stops working, do I know where the original information comes from?
A fallback that nobody remembers how to use is not really a fallback.
Resilience has to be practiced enough that it remains real.
Tool Dependence Becomes a Business Risk
The more useful a tool becomes, the easier it is to build around it.
Heavy dependence on a single tool can become a business risk.
What happens if the price changes?
The features change?
The model changes?
The company changes its policies?
The service goes down?
The tool disappears?
And using several tools does not necessarily mean the system is truly independent.
Different products can still rely on the same underlying provider, infrastructure, or model family.
A workflow can look diversified while still containing a shared point of failure.
The workflow should belong to the work.
Not to the vendor.
Tools can change.
The principles should survive.
Information Risk Grows Too
As workflows become larger, more information moves through them.
Documents.
Sources.
Client information.
Internal notes.
Drafts.
Credentials.
Potentially sensitive material.
That means scaling is not only about productivity.
I also have to think about what information enters the system, who can access it, where it moves, and whether it belongs there in the first place.
More capability creates more responsibility for how information is handled.
Scaling Costs Money Too
There is another side of growth that productivity discussions sometimes ignore.
Cost.
More tools.
More subscriptions.
More storage.
More automation.
More people.
More training.
More maintenance.
More time managing the system.
AI can lower some costs.
It can create new ones too.
A workflow is not scalable simply because it produces more.
The economics have to make sense.
If the cost of maintaining the system grows faster than the value it produces, something needs to change.
Complexity Is a Tax
Every tool adds something.
It may also add:
another login,
another interface,
another failure point,
another subscription,
another set of settings,
another thing to monitor.
Complexity accumulates quietly.
At first, every addition seems useful.
Then the system becomes difficult to understand.
That is why simplicity matters even more as the workflow grows.
The goal should not be to use every tool available.
The goal should be to use the smallest system that can reliably do the work.
Scale What Works
I do not need to scale everything.
That is important.
Some experiments should remain experiments.
Some workflows should be retired.
Some automations should stay small.
Some tasks should remain manual.
The things worth scaling are the things that have demonstrated value.
That means I should know:
Does this improve the work?
Does it save meaningful time?
Does it reduce friction?
Does it protect quality?
Can I maintain it?
Can I explain it?
Can I recover when it fails?
If the answer is no, making it bigger will not fix it.
Slow Growth Can Be Good Growth
There is pressure in technology to move quickly.
Adopt faster.
Automate faster.
Scale faster.
That does not always make sense.
Sometimes slow growth is the responsible choice.
Build one workflow.
Test it.
Measure it.
Fix it.
Then expand.
That may look less impressive than building a giant AI system immediately.
But it creates something more valuable.
Understanding.
I want to know why the system works before I depend on it.
Scaling Vallano Media
For me, this is not theoretical.
I am already thinking about what it means to expand Vallano Media.
More sports coverage.
More publishing.
More AI-assisted workflows.
Potential clients.
Potential collaborators.
More automation.
The system I use today cannot simply be stretched forever.
It has to evolve.
That means this is where I have to apply what I have argued throughout this book.
The lessons cannot exist only on the page.
If I believe verification matters, it has to matter when production increases.
If I believe human authority matters, it has to survive automation.
If I believe workflows need measurement, then growth has to be measured too.
I want technology to increase what Vallano Media can do.
But I do not want growth to weaken the standards behind the work.
That is the challenge.
The Standard Has to Scale Too
This may be the most important point in the chapter.
When output grows, standards have to grow with it.
Verification cannot become optional because there is more work.
Human judgment cannot disappear because automation is convenient.
Editorial control cannot weaken because production is faster.
Transparency cannot become harder because the system is more complicated.
If anything, those things become more important.
Scale should increase capability.
It should not dilute responsibility.
The Journalism Still Has to Matter
There is one final danger.
The workflow could scale successfully.
The systems could become faster.
The automation could work.
The metrics could improve.
And the journalism could become less distinctive.
Less local.
Less ambitious.
Less human.
Less worth reading.
That would not be success.
The workflow exists to support the journalism.
The journalism does not exist to feed the workflow.
If scale makes the work more ordinary, I need to question what I am scaling.
The Final Question
This book began with a simple idea:
The journalist is still responsible.
Everything since then has built on that.
Research.
Drafting.
Verification.
Red-teaming.
Editing.
Human oversight.
Publishing.
Measurement.
Sustainability.
Scaling.
The technology became more capable.
The workflow became more complex.
The potential became larger.
But the central question never really changed.
“Who is responsible for what gets published?”
AI can assist.
Automation can accelerate.
Agents can monitor.
Systems can scale.
But responsibility cannot disappear into the workflow.
Someone still has to decide.
Someone still has to verify.
Someone still has to stop the process when something is wrong.
Someone still has to stand behind the result.
Scaling Without Losing Control
I do not want to build the biggest AI workflow.
I want to build one I understand.
One I can explain.
One I can challenge.
One I can improve.
One I can stop.
One that lets me do more without lowering the standard.
The goal is not total control.
No system gives me that.
The goal is enough visibility to understand what is happening.
Enough authority to intervene.
Enough resilience to recover when something fails.
And enough judgment to know when the system should not continue.
That is what scaling means to me.
Not replacing judgment.
Not removing responsibility.
Not automating everything that can be automated.
It means increasing capacity while protecting the things that matter.
Because the real test of an AI-assisted workflow is not how much it can produce.
It is whether I can still stand behind the work when the system gets bigger.
If I can do more while keeping the standards, the judgment, and the responsibility intact, then the workflow has grown with me.
If I cannot, then I have not really scaled.
I have only lost control.

Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.
Measuring 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.
A workflow can feel productive without actually being productive.
That is one of the traps.
I can move faster.
Generate more drafts.
Create more graphics.
Publish more often.
Use more tools.
Build more automations.
And still end up with a system that is not improving the work.
Activity is easy to see.
Effectiveness is harder.
That is why I need to measure the workflow itself.
Not just how much it produces.
But whether it is helping me produce better work with less unnecessary friction.
The question is not:
“Am I busy?”
It is:
“Is the system actually working?”
Chapter 11 Measured the Change
Earlier in this book, I looked at what changed after I began integrating AI into my work.
Time.
Output.
Capacity.
Repeatability.
Attention.
That gave me useful benchmarks.
But those numbers only tell part of the story.
A workflow can become faster and still become worse.
It can produce more and still create more errors.
It can feel efficient while quietly increasing rework.
It can save time in drafting and lose all of that time in correction.
So measuring the impact of AI is one question.
Measuring the health of the workflow is another.
That is what I want to focus on here.
I Need More Than One Metric
There is no single number that tells me whether the workflow is good.
Time is useful.
But time alone is incomplete.
Output is useful.
But output alone can reward volume.
Traffic may matter.
But traffic does not automatically tell me whether the journalism is accurate or useful.
So I need several signals.
For my workflow, I keep coming back to three broad areas:
Quality.
Time.
Impact.
Those three together tell me much more than any one measurement by itself.
But even that needs restraint.
If measuring the workflow takes more effort than improving the workflow, the measurement system is too heavy.
The goal is not to build a second workflow just to watch the first one.
Quality Comes First
If the workflow is faster but the work gets worse, I have not improved anything.
So quality has to come first.
That means asking questions like:
Did I catch factual problems before publication?
Did the central claims survive verification?
Did the red-team pass expose anything important?
Did the final article preserve the meaning of the evidence?
Did the graphic accurately represent the story?
Did I publish the correct version?
Did I have to issue a correction?
Did I overlook something that the workflow should have caught?
These are not always easy to reduce to a number.
That is fine.
Not every useful measurement needs to become a score.
Sometimes the most useful record is simply:
What went wrong?
Where did it happen?
Why did the workflow miss it?
Corrections Are Useful Data
Nobody wants to make an error.
A correction is a failure in the published work.
But it can still produce useful information about the workflow.
Where did the mistake enter?
Research?
Drafting?
Verification?
Editing?
Graphic production?
Scheduling?
Was the source wrong?
Did I misread the source?
Did AI introduce the error?
Did I approve something too quickly?
Did the wrong version get published?
The correction itself matters.
But so does understanding how it got through.
That is how a workflow improves.
And no corrections does not automatically mean no errors.
A problem may simply have gone unnoticed.
That is another reason not to treat one metric as proof that the system is healthy.
Near-Misses Matter Too
Not every important problem reaches publication.
Sometimes the workflow catches it first.
That is a success.
A bad statistic caught during verification.
A misleading headline caught during red-teaming.
A strange graphic caught during QC.
A sentence that changes meaning during editing.
A weak source discovered before publication.
Those near-misses are worth recording.
They tell me which safeguards are actually doing useful work.
But their numbers can be deceptive.
More detected problems can sometimes mean the safeguard improved, not that the journalism declined.
If the truth pass suddenly starts finding more weak claims, that may mean I have a bigger problem.
Or it may mean the truth pass has become better at finding them.
The number needs interpretation.
And if a check rarely catches anything, I should not automatically remove it.
It may be unnecessary.
Or it may protect against a low-frequency, high-consequence problem.
I need to know which.
Time Still Matters
Quality comes first.
But time still matters.
A workflow that produces excellent work but takes twice as long as necessary may not be sustainable.
So I want to know:
How long does research take?
How long does drafting take?
How long does verification take?
How much time goes into rework?
How many graphic revisions are needed?
How long does the full publication package take?
Where does the process slow down?
I do not need to time every article forever.
But periodic timing gives me useful benchmarks.
The goal is not to race the clock.
The goal is to understand where the time goes.
And there is one caution I need to remember:
“Precision in the number does not create precision in the conclusion.”
I can know that something took exactly 36 minutes and 54 seconds.
That does not mean I can make an equally exact claim about why it took that long.
Measure Rework, Not Just First-Pass Speed
This has become especially important.
A fast first draft can look impressive.
But if I spend another hour fixing it, the first-draft time does not tell me much.
The same applies to graphics.
A graphic generated in seconds is not efficient if it takes six attempts to get one usable version.
So I need to think about rework.
How many times did I have to go back?
What caused the revision?
Was the problem predictable?
Could the instruction have been better?
Could the workflow have caught the issue earlier?
A system that gets the work closer to right the first time may be more valuable than one that produces the first version fastest.
Bottlenecks Tell Me Where to Look
Every workflow develops bottlenecks.
The slowest point may not stay the same forever.
Early on, drafting may be the problem.
Later, verification may become the bottleneck.
Then graphics.
Then version control.
Then publishing.
A recurring bottleneck is one place I should investigate for possible improvement.
That does not mean the slowest stage is automatically broken.
Verification may be slow because the reporting requires care.
The answer may not be to shorten it.
Sometimes the answer is better organization.
Better instructions.
Better source access.
Better documentation.
A better tool.
Or a simpler process.
Measurement tells me where to look.
Judgment tells me whether something actually needs to change.
Output Needs Context
I can count articles.
Posts.
Graphics.
Chapters.
Social updates.
That is useful.
But output needs context.
More finished work may indicate better capacity.
Or it may indicate that I am publishing too much.
So I need to ask:
Did the additional output maintain the standard?
Was it necessary?
Was it useful?
Did it create more correction work?
Did it reduce the time available for higher-value reporting?
The number itself is not the answer.
It is a signal.
Impact Is Harder to Measure
Impact is probably the hardest part.
What did the work actually do?
Did people read it?
Did they spend time with it?
Did they share it?
Did it lead to another conversation?
Did a source respond?
Did someone contact me because of it?
Did the article help establish credibility?
Did it support the larger business?
Did it make the next piece easier to produce?
Not every article needs the same kind of impact.
A sports recap may serve a different purpose than an AI journalism essay.
A book chapter may be building long-term authority rather than immediate traffic.
A business article may support a service offering.
So impact has to be measured against the purpose of the work.
“Impact should be interpreted, not simply counted.”
Traffic Is Not the Same as Value
This matters to me.
A high-traffic article may be valuable.
A low-traffic article may also be valuable.
Traffic is one signal.
It is not the entire score.
A piece may reach a small audience but the right audience.
It may create a business lead.
It may strengthen expertise.
It may become part of a larger book.
It may be cited later.
It may perform slowly over time.
So I want to be careful about letting page views decide what deserves to exist.
The purpose comes first.
Then I measure whether the work served that purpose.
Some Measures Happen Before Publication. Others Come After.
There are really two sides to measurement.
Some signals tell me what is happening inside the workflow.
Verification problems.
Rework.
Headline changes.
Graphic errors.
Weak sources.
Those are visible before publication.
Other signals arrive later.
Corrections.
Reader response.
Traffic.
Business inquiries.
Long-term usefulness.
Those tell me what happened after the work reached the audience.
I need both.
Internal measurements tell me how the process behaved.
External measurements help tell me what the work accomplished.
The Workflow Should Reduce Avoidable Errors
One useful long-term question is simple:
Am I making fewer preventable mistakes?
Not zero mistakes.
That is not realistic.
But fewer mistakes caused by:
missing a basic fact,
using the wrong version,
skipping verification,
forgetting a disclosure,
publishing the wrong graphic,
or accepting an AI-generated claim without checking it.
If those problems decrease, the workflow may be doing something useful.
If they keep happening, the system needs attention.
I Can Measure Consistency
Another question:
Do I follow the process consistently?
Not perfectly.
But consistently enough that I know what standard the work went through.
That includes:
verification,
red-teaming,
voice editing,
QC,
final approval.
If some articles get the full process and others skip important safeguards without a reason, the workflow is not really stable.
Consistency does not mean identical treatment.
It means the appropriate standard is applied intentionally.
An unusual story should not be treated as a workflow failure simply because it does not fit the normal benchmark.
Some work deserves a different path.
I Can Measure Friction
This is less obvious.
What part of the workflow annoys me?
Where do I hesitate?
What do I keep avoiding?
What feels harder than it should?
Those feelings can reveal design problems.
If I keep avoiding documentation, maybe it is too complicated.
If I keep skipping a check, maybe the check needs to be redesigned.
If a tool constantly interrupts the process, maybe it does not belong.
Friction is not always bad.
Verification is sometimes slow because verification needs to be slow.
The goal is to remove unnecessary friction.
Not necessary care.
I Can Measure Cognitive Load
This is harder to quantify, but I can still observe it.
Do I feel like I am juggling too many things?
Am I constantly wondering what comes next?
Am I keeping too many unfinished tasks in my head?
Do I lose track of which version is final?
Does the workflow make the work feel more organized or more chaotic?
A strong system should reduce unnecessary mental clutter.
If automation creates more monitoring than it removes, that matters.
If five tools require five different kinds of attention, that matters too.
The workflow should give attention back.
Not consume all of it.
I Can Measure Reliability
Does the system work when I need it?
That includes the technology.
But it also includes the process.
Can I still publish if one tool is unavailable?
Can I verify a claim manually?
Can I recover if an automation breaks?
Can I identify the final version?
Can I explain what happened?
Reliability should not mean every story follows the same path.
It should mean the workflow responds predictably when something goes wrong.
A fast system that constantly breaks is not efficient.
It is fragile.
I Should Measure the System, Not Perform for the Metric
There is a danger in measurement.
Once I start tracking something, I can start optimizing for it.
If I measure speed, I may rush.
If I measure output, I may publish more than I should.
If I measure traffic, I may chase clicks.
If I measure correction rate, I may become too cautious.
So the metrics have to serve the work.
The work should not serve the metrics.
And the moment a metric becomes something I am trying to win, I need to question whether it is still helping me.
Measurement should help me ask better questions.
Not create a game I am trying to beat.
Metrics Need Maintenance Too
A useful metric today may become less useful later.
The workflow changes.
The assignments change.
My experience changes.
The technology changes.
So the measurements need review too.
Does this number still tell me what I think it tells me?
Is this benchmark still comparable?
Am I measuring something simply because I have always measured it?
A metric should earn its place just like a workflow step should.
A Simple Workflow Scorecard
I do not need a complicated dashboard.
A simple review can tell me a lot.
After a project, I can ask:
“Quality”
– Did the work meet the standard?
– What errors or near-misses occurred?
– What did the workflow catch?
“Time”
– How long did the major stages take?
– Where did I lose time?
– How much rework was required?
“Impact”
– Did the work achieve its purpose?
– What happened after publication?
– Was the result worth the effort?
Then one more question:
“What should I change next time?”
That last question turns measurement into improvement.
The Workflow Should Improve Over Time
If I collect data but never change anything, the measurement does not do much.
The point is not to create reports about the workflow.
The point is to make the workflow better.
Maybe I discover that graphic revisions are taking too long.
I improve the design specification.
Maybe verification repeatedly finds missing dates.
I add a date check earlier.
Maybe social copy keeps overstating the headline.
I add a comparison against the locked manuscript.
Maybe one automation rarely saves time.
I remove it.
Measurement should lead to decisions.
Remove What Does Not Help
This is just as important as adding improvements.
Workflows tend to grow.
They rarely shrink on their own.
A new problem creates a new step.
A new tool creates a new process.
A new idea creates another check.
Eventually I need to ask:
What can go?
If a step no longer protects the work, improves the work, or saves meaningful effort, it may not deserve to remain.
Measurement gives me permission to simplify.
That is part of sustainability too.
Look for Trends, Not One-Off Results
One article does not prove much.
Neither does one perfect graphic.
Or one terrible day.
I want patterns.
Are production times gradually falling?
Is rework decreasing?
Are the same errors recurring?
Is verification catching problems earlier?
Are graphics requiring fewer revisions?
Is the workflow handling more work without becoming chaotic?
That is more useful than reacting to every individual result.
The goal is not perfection.
The goal is direction.
The Numbers Need Notes
A number without context can mislead me.
Thirty minutes may be fast.
Or it may be slow.
It depends on the assignment.
So when I record a benchmark, I also need to know what happened.
Was the research already complete?
Was the topic familiar?
Did an interview delay the process?
Did a tool fail?
Was the story unusually simple?
Did I have to redo the graphic?
Context keeps the number honest.
I Am Measuring My Own System
There is another limitation I need to remember.
I am both using the workflow and evaluating it.
That means I can be biased toward believing the system I built is working.
I may notice the successes more readily than the failures.
I may explain away a weak result because I know how much work went into the process.
So I have to be alert to the possibility that I am seeing what I want to see.
That does not make self-measurement useless.
It means I should document enough evidence that I can challenge my own interpretation.
Measurement Should Include What AI Gets Wrong
If I am measuring an AI-assisted workflow, I should track AI failures too.
Not every typo.
Not every awkward sentence.
Not every useless suggestion.
That would become its own job.
I care more about recurring or consequential failures.
Fabricated details.
Bad source suggestions.
Overconfident summaries.
Voice drift.
Weak headline recommendations.
Graphic text errors.
Misleading visual choices.
Repeated failures tell me where AI needs tighter supervision.
And an AI mistake is not automatically a workflow failure if the workflow catches it before publication.
Sometimes catching the mistake is evidence that the safeguard worked.
Measurement Should Include What AI Does Well
The opposite matters too.
Where is AI consistently useful?
Organizing notes?
Finding contradictions?
Creating alternative structures?
Cleaning up grammar?
Generating first-pass graphics?
Repeated success in a specific task may justify greater operational confidence in that task.
But success in one task should not automatically expand trust into another.
A system that organizes notes well has not proved that it should decide which source is credible.
A tool that produces useful headline options has not earned authority over publication.
Trust has to remain specific.
Trust Should Be Specific
I do not want to say:
“I trust AI.”
That is too broad.
I may trust one workflow for one type of task under one set of conditions.
That is different.
I may trust AI to organize my notes.
But not to establish the facts.
I may trust it to suggest headlines.
But not to decide which headline gets published.
I may trust it to flag a possible contradiction.
But not to resolve the contradiction without checking the sources.
Measurement helps make that confidence more specific.
And the required checks remain even when a task has performed well repeatedly.
The Journalism Cannot Become More Ordinary
There is one more thing I do not want measurement to erase.
Ambition.
Originality.
Work that does not fit the normal template.
A workflow can become cleaner and more efficient while the journalism becomes more ordinary.
That would not be success.
Some stories deserve more time.
Some projects deserve more experimentation.
Some reporting will never fit neatly inside the average benchmark.
I do not want an unusual story to look like a failure simply because it took longer.
The workflow should support ambitious journalism.
Not train me to avoid it.
The Workflow Has to Produce More Than Activity
This is what I keep coming back to.
A busy workflow can look impressive.
Multiple agents.
Automations.
Dashboards.
Prompts.
Checklists.
Constant output.
But none of that matters if the work does not improve.
I want a system that produces:
better decisions,
fewer avoidable mistakes,
less unnecessary rework,
more usable capacity,
and journalism I am willing to defend.
That is what I am measuring.
Measuring the Workflow
So how do I know whether my AI-assisted workflow is actually working?
I look beyond speed.
I look beyond output.
I look beyond whether the technology did something impressive.
I ask:
Is the quality holding?
Is the process becoming easier to repeat?
Is rework decreasing?
Are problems being caught earlier?
Am I using my time better?
Is the work achieving its purpose?
Is the system still under control?
Those questions tell me more than any productivity number by itself.
Because a workflow is not successful simply because it keeps me moving.
It is successful when it helps me move in the right direction.
And measurement is useful only when it helps me see whether I still am.

Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.
Building a Sustainable 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 workflow can look great on paper.
Research.
Draft.
Verify.
Red-team.
Edit.
Quality control.
Publish.
Clean.
Logical.
Complete.
But there is another question that matters just as much:
“Can I keep doing it?”
A good workflow is not simply one that works once.
It is one that still works when I am tired.
Busy.
Under deadline.
Covering multiple projects.
Learning a new tool.
Fixing a mistake.
Or dealing with something I did not plan for.
That is where sustainability begins.
A Workflow Has to Survive Real Life
The easiest workflow to build is the ideal workflow.
The harder one is the workflow that works when the day is messy.
A sustainable system has to survive interruptions.
Unexpected reporting.
Technical problems.
A slow source response.
A graphic that needs to be redone.
A deadline that moves.
A story that becomes more complicated than expected.
If the workflow only works under perfect conditions, it is not really a workflow.
It is a demonstration.
I need something I can use again tomorrow.
Repeatability Matters More Than Complexity
There is a temptation to make workflows more complicated as the tools become more capable.
Add another AI role.
Add another check.
Add another prompt.
Add another automation.
Add another layer.
Sometimes that helps.
Sometimes it just creates more work.
A sustainable workflow should be detailed enough to protect quality, but simple enough that I can actually use it consistently.
That balance matters.
If a system requires too much effort to maintain, eventually I will stop using it.
Then all of the sophistication becomes irrelevant.
Every new step should have to justify the time and complexity it adds.
The Workflow Has to Earn Its Place
Every stage should answer a question.
Research: What do I need to know?
Draft: What is the story?
Verification: What can I prove?
Red-team: What might be wrong?
Editing: Is this clear and still mine?
Quality control: Is the complete package ready?
Publish: Am I willing to stand behind it?
If a step does not improve the work, protect the work, or make the process easier to repeat, I need to ask why it exists.
That is one of the ways I keep the workflow from becoming bloated.
Not every possible check belongs in every story.
Not every tool belongs in every workflow.
Not every new AI feature needs to be added just because it exists.
Complexity has to earn its place.
Build Around the Work, Not the Tool
This has become one of my most important rules.
Do not build the workflow around the AI tool.
Build it around the work.
Tools change.
Features disappear.
Models improve.
Interfaces change.
Subscriptions change.
Companies change direction.
If my entire workflow depends on one exact feature working forever, then the system is fragile.
The real structure should be independent of the tool whenever possible.
I need research.
I need verification.
I need challenge.
I need editing.
I need quality control.
I need final human approval.
Which tool assists me at each stage can change.
The principles should survive the software.
But complete tool independence is not always realistic.
A workflow may become more efficient because of a particular platform or feature.
That is fine.
The important thing is knowing where that dependency exists.
If one tool disappears tomorrow, what breaks?
That is a question worth being able to answer.
Start With the Problem
Many of the workflows I now use did not begin because I sat down and decided to create a workflow.
They began because something kept happening.
I needed a better way to verify claims.
That became part of the truth process.
I needed something to challenge the story instead of agreeing with it.
That became red-teaming.
I needed a better way to check whether AI-generated writing still sounded like me.
That became part of the voice and editing process.
I needed to prevent graphics from slipping through with obvious errors.
That became visual quality control.
The workflow grew from problems.
That is important.
I was not collecting workflows.
I was solving recurring problems.
A Workflow Can Reduce What I Have to Hold in My Head
One of the biggest benefits of a repeatable system is that I do not have to remember everything every time.
Without a workflow, I have to keep asking myself:
Did I verify that?
Did I challenge the headline?
Did I check the graphic?
Did I review the source?
Did I make sure the final version is the one being published?
That creates mental load.
A good workflow can move some of that burden out of my head and into the process.
The process reminds me.
That does not remove judgment.
It protects my attention so I can use judgment where it matters.
Checklists Help, but They Are Not the Workflow
Checklists are useful.
I use them.
But a checklist is not the entire system.
Checking a box does not prove the work was done well.
“Verify” is meaningless if I do not actually reopen the source.
“Red-team” means nothing if I ignore every criticism.
“QC complete” means nothing if I rushed through it.
The checklist provides structure.
The quality still depends on the thinking inside each step.
That is why I keep returning to the same principle:
Process supports judgment.
It does not replace it.
Sustainability Requires Different Levels of Review
Not every piece of work needs the same amount of scrutiny.
A short social post does not need the same process as a deeply reported article.
A routine game recap may not require the same review as a story involving an accusation.
A graphic caption does not require the same level of verification as a major factual claim.
A sustainable workflow has to recognize that.
Otherwise, the process becomes too heavy.
I need a baseline standard.
Then I need the ability to increase scrutiny when the stakes increase.
That makes the system both responsible and usable.
Consistency should not become uniformity.
Some stories need a different process.
The Baseline Cannot Disappear
Risk-based review does not mean no review.
There still has to be a minimum.
Basic facts.
Names.
Dates.
Numbers.
Attribution.
Headline accuracy.
Graphic accuracy.
Disclosure where appropriate.
Final human review.
Those are not optional simply because the story seems easy.
Simple work can still contain mistakes.
A lightweight workflow is still a workflow.
Build Loops, Not Just Steps
Workflows are often drawn as straight lines.
Research → Draft → Verify → Edit → Publish.
Real work does not behave that neatly.
Verification can send me back to research.
Red-teaming can expose a missing source.
Editing can reveal a factual problem.
Quality control can uncover the wrong version.
A graphic can force me to reconsider the framing.
So I think less about a straight line now and more about loops.
The system moves forward.
But it also needs a way to move backward.
That flexibility is part of what makes it sustainable.
The Workflow Should Make Failure Visible
A bad workflow hides problems.
A good one exposes them.
I want to know when:
the source is weak,
the claim is unsupported,
the story is not ready,
the graphic is wrong,
the headline is overstated,
the AI recommendation is unreliable,
or the workflow itself is failing.
A workflow also has to assume that polished AI output can still be wrong.
That matters because a system that always reports success is not useful.
Sometimes the correct output is:
Not ready.
Needs more reporting.
Needs another source.
Needs another edit.
Needs to be stopped.
That is not the workflow failing.
That is the workflow doing its job.
Repeatability can create confidence.
Confidence should not become complacency.
The eleventh use still deserves judgment, even if the first ten went smoothly.
I Need to Know Where the Bottlenecks Are
A sustainable system also requires observation.
Where am I losing time?
Where do mistakes keep happening?
What stage causes the most rework?
What part feels unnecessarily complicated?
What keeps getting skipped?
Those are signals.
If graphics repeatedly require five revisions, I may need a better design specification.
If source verification keeps slowing the workflow, I may need better source organization.
If I keep rewriting AI-generated copy because it loses my voice, I may need a better editing instruction.
The workflow itself needs editing.
A Useful Workflow Is Rarely Permanently Finished
This is something I did not fully understand when I first started building systems.
I thought the goal was to create the workflow.
Now I think the goal is to maintain it.
The workflow changes as I learn.
It changes when the technology changes.
It changes when I make mistakes.
It changes when I find a faster approach that does not weaken the standard.
It changes when a new risk becomes obvious.
That does not mean the system has to be constantly rebuilt.
It means I should be willing to improve it when the evidence says I should.
Maintenance Is Part of the Cost
A workflow is not free once it exists.
Prompts need updating.
Automations can break.
Documentation gets old.
Tools change.
Processes that once saved time can become unnecessary.
That maintenance cost counts.
A system that saves ten minutes every day but requires hours of constant repair may not be as efficient as it appears.
A workflow should reduce friction overall.
It should not simply move the friction into maintenance.
Stable Principles, Flexible Methods
That is the balance I want.
Stable principles.
Flexible methods.
The principles stay:
Verify.
Challenge.
Maintain accountability.
Protect the meaning.
Keep human authority.
Correct mistakes.
Do not publish what I cannot defend.
The methods can change.
One AI tool may become another.
A manual step may become partially automated.
A checklist may become a dashboard.
A prompt may become an agent.
A graphic workflow may improve.
The methods evolve.
The standard remains.
Automation Should Remove Repetition, Not Oversight
Automation becomes useful when it removes repetitive work.
Monitoring.
Sorting.
Formatting.
Organizing.
Flagging.
Scheduling.
Preparing.
But I do not want automation to quietly remove the checkpoints that protect the journalism.
That distinction matters.
The goal is not:
Automate everything.
The goal is:
Automate what can be handled safely without removing the points where my judgment still matters.
Sometimes that will mean automation.
Sometimes the simplest reliable step will still be manual.
Not every repeatable task deserves an agent.
Automation Creates Dependencies
There is another side to automation.
The more connected the workflow becomes, the more a single failure can travel through the system.
A bad input can affect a summary.
The summary can affect the draft.
The draft can affect the headline.
The headline can affect the social copy.
One early problem can move downstream quickly.
That does not mean automation is a bad idea.
It means dependencies need to be visible.
I need to know which steps rely on which other steps.
And where I can interrupt the chain.
The More Automated the System, the More Visible the Controls Should Be
As workflows become more automated, it becomes more important that their control points remain visible and usable.
Where does verification happen?
Where can I reject the draft?
Where can I stop publication?
Where do I approve the graphic?
Where do I see which version is final?
Where do I know what AI contributed?
If I cannot answer those questions, the system may be efficient but difficult to control.
That is not sustainable.
A Sustainable Workflow Needs a Fallback
The happy path is easy.
Everything works.
The source is available.
The AI tool responds.
The automation runs.
The graphic generates correctly.
The publishing system behaves.
But systems fail.
What happens when the AI tool is unavailable?
What happens when an automation breaks?
What happens when the source disappears?
What happens when the wrong version is scheduled?
What happens when the graphic system fails on deadline?
A sustainable workflow needs a fallback.
Sometimes that fallback is another tool.
Sometimes it is a manual process.
Sometimes it means slowing down.
Sometimes it means not publishing yet.
The important thing is that one failure does not automatically destroy the entire process.
Documentation Matters
A workflow becomes easier to maintain when I can explain it.
What happens first?
What happens next?
What requires human approval?
What sources are acceptable?
What does “locked” mean?
What happens when something fails?
What gets recorded?
The process should not exist only in my memory.
Documentation creates consistency.
It also makes the system easier to teach.
But documentation only helps if it stays current.
An outdated instruction can create as much confusion as no instruction at all.
A Workflow Should Be Teachable
This is another test I have started to think about.
Could I explain the workflow to someone else?
Could another person understand:
what each stage does,
why it exists,
where AI helps,
where the human decides,
and what happens when something goes wrong?
If the answer is no, the workflow may be too dependent on intuition.
Intuition will always matter.
But a sustainable system needs enough structure that someone else can understand how it operates.
That matters even more if only one person currently knows how everything works.
If nobody else can understand or repair the system, that is a hidden weakness.
Sustainability Also Means Not Burning Myself Out
This part matters.
A workflow is not sustainable if it produces more work than I can responsibly carry.
AI can increase capacity.
That can create a new temptation:
Fill all the capacity.
More articles.
More projects.
More posts.
More experiments.
More workflows.
More everything.
That can defeat the purpose.
Efficiency should not automatically become workload expansion.
A sustainable system should make the work easier to manage.
Not simply make it possible to overload myself more efficiently.
Capacity Needs Limits
This is where measurement becomes important.
How much can I actually manage well?
Not how much can I technically produce.
How much can I verify?
How much can I review?
How much can I publish without lowering the standard?
How much can I keep track of without losing control?
Those questions define capacity better than raw output.
A sustainable workflow respects those limits.
The System Should Protect the Important Work
The purpose of efficiency is not to do everything.
It is to create room for what matters.
More reporting.
Better verification.
Stronger editing.
Deeper thinking.
Strategic planning.
Learning.
Rest.
Sometimes the best use of a faster workflow is not another article.
Sometimes it is having enough space to do the existing work better.
Build for the Bad Day
I think this may be one of the best tests of a workflow.
Does it still work on the bad day?
Not the perfect morning when I have energy, time and no interruptions.
The bad day.
The deadline day.
The tired day.
The day when three things happen at once.
The day when the first graphic is wrong.
The day when the source responds late.
The day when the AI gives me a bad answer.
That is when structure matters most.
But there is another test too.
What happens when the workflow itself is causing the bad day?
If maintaining the system becomes a constant burden, something needs to change.
The workflow should support the work.
The work should not exist to support the workflow.
Simplicity Is a Form of Strength
A sustainable workflow does not need to look impressive.
It needs to work.
The best systems are often boring.
Clear stages.
Clear standards.
Clear responsibility.
Clear stopping points.
Clear ways to recover when something goes wrong.
That is enough.
Complexity should earn its place.
If it does not make the work better, safer, clearer or easier to manage, I do not need it.
The Workflow Has to Belong to Me
There is no universal perfect AI workflow.
Different journalists.
Different newsrooms.
Different beats.
Different risks.
Different resources.
Different standards.
What works for me may not fit someone else exactly.
That is fine.
The point is not to copy my workflow line by line.
The point is to understand the principles well enough to build one that fits the work.
The workflow should reflect:
what I produce,
what risks I face,
what standards I follow,
what tools I use,
and where I need human judgment.
That is what makes it usable.
The Journalism Still Has to Be Good
This is the ultimate test.
A workflow can become faster.
Cleaner.
More automated.
More repeatable.
And still produce worse journalism.
That is possible.
A smooth system is not automatically a good system.
The workflow should be judged by whether it protects the quality of the journalism, not by how smoothly the machinery runs.
Does the reporting remain strong?
Does the evidence survive?
Does the writing remain specific?
Does the process catch mistakes?
Does the system leave room for stories that do not fit the template?
If not, the workflow needs to change.
Sustainable Means I Can Trust the Process
Not blindly.
Never blindly.
But I can trust that the process will ask the right questions.
Did I verify this?
Did I challenge it?
Did I preserve the meaning?
Did I inspect the final product?
Did I keep control of the decision?
Is this ready?
That is what I want from a workflow.
Not a machine that guarantees correctness.
A system that repeatedly puts me in the position to make better decisions.
Building a Workflow That Lasts
A sustainable AI-assisted workflow is not built by adding every new tool.
It is built by knowing what the work requires.
Protecting the important checkpoints.
Reducing unnecessary friction.
Learning from mistakes.
Maintaining the system.
Knowing when to automate.
Knowing when not to.
And remembering that efficiency is useful only if the work remains worth publishing.
The tools will change.
The workflow will evolve.
The methods will improve.
But the principles underneath the system need to survive all of that.
Because the best workflow is not the fastest.
Or the most automated.
Or the most complicated.
It is the one I can keep using, adapting and understanding without losing the standards that made the work worth doing in the first place.

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

What the Jubilee Debate Revealed About Work, Wealth, and AI
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 Debate About More Than Generational Differences
When businessman and Shark Tank investor Kevin O’Leary appeared on Jubilee Media’s “Surrounded” series on November 15, 2026, he faced 20 Generation Z workers in a discussion about wealth, employment, work-life balance, and professional success.
The episode, titled “1 Millionaire Boss vs 20 Gen Z Workers”, explored disagreements about whether hard work can make anyone wealthy, whether competence matters more than passion, and how much influence personal values should have over employment decisions.
Some exchanges became confrontational.
Yet beneath the disagreements were questions that entrepreneurs and working professionals have confronted for generations.
And in an era of increasingly capable artificial intelligence, what advantages remain exclusive to experienced business professionals?
O’Leary approached the discussion from the perspective of an established entrepreneur and investor.
The participants offered a range of individual perspectives shaped by their experiences and concerns about the modern workplace.
Neither O’Leary’s business record nor the participants’ personal experiences automatically establishes the accuracy of every argument.
The more useful approach is to examine the claims themselves.
For entrepreneurs, the debate provided an opportunity to distinguish between principles that sound persuasive and strategies that can withstand practical scrutiny.
Hard Work Matters. Opportunity Matters Too.
One of the debate’s central disagreements concerned the relationship between hard work and wealth.
O’Leary emphasized the importance of effort, discipline, and personal responsibility in achieving financial success.
Those qualities are important to entrepreneurship.
Building a business often requires substantial time before meaningful revenue appears.
Entrepreneurs must identify customers, establish relationships, manage expenses, and continually adjust their operations.
However, effort does not guarantee a particular financial outcome.
Two people may demonstrate comparable discipline while facing different economic circumstances.
One might have access to affordable financing, experienced mentors, established professional networks, and a growing customer base.
Another may face higher borrowing costs, limited financial reserves, and fewer opportunities.
These differences can influence business outcomes without eliminating the importance of individual decisions.
Economic pressures also affect employees.
According to a Congressional Research Service analysis of Census data, 49.4% of U.S. renter households were considered housing-cost burdened in 2024, meaning they spent more than 30% of household income on housing costs.
That statistic does not describe every worker’s financial circumstances, nor does it establish the situation of any individual Jubilee participant.
It does demonstrate why discussions about wages, savings, career advancement, and economic opportunity require more than assumptions about motivation.
A worker struggling to cover essential expenses may have less flexibility to pursue additional training, relocate, or finance a new business.
Hard work remains important.
But its economic rewards are influenced by circumstances that extend beyond effort alone.
For entrepreneurs, recognizing those conditions is not an excuse to avoid responsibility.
It is part of understanding the environment in which a business operates.
What College Football Can Teach Us About Business Competition
Sports provide a useful illustration of the relationship between resources and execution.
Consider two college football programs preparing for a season.
Both have coaches developing strategies, players attending practices, and athletic departments working to improve performance.
However, the programs may operate with significantly different budgets, facilities, recruiting resources, and support personnel.
Those differences can affect their ability to attract talent, develop athletes, and maintain competitive depth.
A smaller program cannot necessarily eliminate a resource disadvantage simply by asking its players and coaches to work harder.
At the same time, a larger budget does not guarantee victories.
A well-funded program can underperform because of poor decisions, ineffective preparation, or inconsistent execution.
A program with fewer resources may outperform expectations through player development, effective coaching, and disciplined organization.
The comparison has limitations.
Athletic competition operates under established rules and produces measurable results, while businesses face changing markets and different definitions of success.
Nevertheless, the underlying principle remains useful.
Resources influence what an organization can attempt.
Strategy determines how those resources are deployed.
Execution influences whether the organization achieves its objectives.
A small business may not have the advertising budget, personnel, or financial reserves of a major corporation.
But it may still compete effectively by concentrating on a specialized market, building strong customer relationships, and delivering services that larger competitors overlook.
That approach does not eliminate financial disadvantages.
It recognizes that organizations must make strategic decisions based on the resources they actually possess.
The ChatGPT Question: What Does an Investor Really Provide?
One of the episode’s most revealing exchanges involved a software engineer who questioned the value of an investor when artificial intelligence can assist with business planning.
According to contemporary reporting by BuzzFeed and The Daily Wire, the participant asked whether ChatGPT could analyze a business plan and challenged O’Leary to explain what he contributed.
The exchange, also reflected in screenshots of a social-media post showing the discussion, began with O’Leary explaining that he looks for passionate individuals with promising business plans.
The participant questioned whether ChatGPT could perform the analytical portion of that process.
O’Leary reportedly answered with a single word: “Money.”
The participant then questioned why entrepreneurs should depend on wealthy investors and whether alternative sources of financing should be more accessible.
The exchange illustrated two different questions that should not be confused.
The first concerns the analytical and advisory value of experienced investors.
The second concerns access to capital and the influence that wealthy investors may exercise over entrepreneurs seeking financing.
Artificial intelligence has made certain business-planning capabilities more accessible.
An entrepreneur can use ChatGPT to develop an initial business model, examine pricing strategies, identify possible weaknesses, explore financial scenarios, and prepare questions for potential investors.
For a small-business owner without the resources to hire specialists for every preliminary task, that assistance can be valuable.
However, producing an analysis is not the same as establishing its accuracy.
An AI-generated financial forecast may look convincing while relying on unrealistic revenue expectations, incomplete expense estimates, or unsupported assumptions about customer demand.
ChatGPT can also misunderstand instructions, overlook relevant information, or generate inaccurate claims.
The entrepreneur must understand the underlying business well enough to challenge the output.
That means checking calculations, verifying market information, questioning assumptions, and obtaining appropriate professional advice when the stakes require it.
A polished business plan does not automatically represent a viable business.
Yet recognizing AI’s limitations does not resolve the participant’s broader concern about financing.
An investor may provide money that allows a company to purchase equipment, hire employees, expand operations, or enter new markets.
Experienced investors may also contribute industry knowledge, professional relationships, and operational guidance.
But those benefits are not automatic.
An investment arrangement may require the entrepreneur to surrender equity, accept restrictions on decision-making, or share control over the company’s future.
The entrepreneur must evaluate whether the capital and additional support justify those costs.
Private equity investment is also not the only financing option.
Depending on their circumstances, entrepreneurs may consider commercial loans, Small Business Administration-backed financing, reinvested earnings, or other funding arrangements.
Each option involves eligibility requirements, costs, risks, and potential trade-offs.
Access to financing remains a practical challenge for many small businesses.
According to the Federal Reserve Banks’ “2026 Report on Employer Firms“, based on the 2025 Small Business Credit Survey, 42% of surveyed financing applicants received the full amount requested, while 36% received some or most and 22% received none.
These findings demonstrate why access to capital cannot be separated from discussions about entrepreneurship.
Having a viable business idea does not automatically mean obtaining the financing necessary to pursue it.
The participant’s broader argument also deserves recognition because he explicitly distinguished his own goals from entrepreneurship.
According to contemporary reporting, he said he did not want to become an entrepreneur; he wanted to live his life.
That distinction matters.
Not everyone wants to own a business, pursue venture capital, or become wealthy.
Workers can reasonably seek financial stability, fair compensation, and opportunities for advancement without aspiring to become entrepreneurs.
The question is not whether ChatGPT can replace an investor.
It is which responsibilities an entrepreneur can handle independently, which resources the business actually needs, and what the entrepreneur is willing to exchange to obtain them.
AI Is a Gold Mine of Possibilities, Not Guaranteed Profits
Artificial intelligence represents a significant opportunity for entrepreneurs, particularly those operating smaller organizations.
Tasks that once required substantial time can now be supported by tools that assist with research, planning, drafting, analysis, and workflow organization.
But the availability of powerful technology does not automatically create a successful business.
There is a difference between using AI and understanding how to integrate it into an operation.
Consider a digital publishing company.
AI can help organize research, identify inconsistencies, review drafts, analyze information, and prepare content for distribution.
These capabilities may allow a small publishing operation to work more efficiently without immediately expanding its staff.
However, AI does not remove the publisher’s responsibility for accuracy.
If inaccurate information reaches the public, the organization’s reputation may suffer regardless of which technology helped produce it.
The same principle applies to consulting, hospitality, retail, and professional services.
A business owner can use AI to examine customer-service procedures, develop training materials, or identify potential operational improvements.
But those recommendations must be tested against the realities of the business.
Technology becomes valuable when it helps solve an actual problem.
That requires identifying the problem, understanding the customer or organization, selecting an appropriate tool, and evaluating whether the results justify the investment.
Although AI systems can generate recommendations and increasingly perform tasks autonomously, business owners remain responsible for establishing appropriate oversight, verifying consequential information, and deciding how the technology should be used within their organizations.
Entrepreneurs who treat AI as an automatic source of wealth risk overlooking the fundamentals of business development.
A company still needs customers, revenue, effective operations, and a product or service that delivers meaningful value.
AI can support those objectives.
It cannot guarantee them.
Passion, Competence, and Professional Credibility
Another major disagreement in the debate concerned the relative importance of passion and competence.
O’Leary emphasized the importance of being good at one’s work.
There is a practical business argument behind that position.
Customers generally expect reliable service, accurate information, and products that meet their needs.
An entrepreneur’s enthusiasm does not compensate indefinitely for missed deadlines, poor service, or repeated mistakes.
However, passion and competence do not have to compete.
Interestingly, O’Leary’s own explanation of his investment approach reinforces that distinction.
In the exchange about business plans, he described looking for people who demonstrate passion and present promising business ideas.
That suggests passion can have value in identifying entrepreneurial potential, even when competence and execution remain necessary to determine whether the business can succeed.
Passion can motivate someone to study an industry, develop specialized knowledge, and continue improving over time.
Competence allows that individual to turn enthusiasm into work that others can rely upon.
Sports journalism offers a useful example.
A reporter may have a lifelong interest in college athletics and enjoy covering games, interviewing coaches, and studying team histories.
But enthusiasm alone does not establish professional credibility.
The reporter must verify statistics, accurately represent interviews, distinguish reporting from opinion, and understand the context surrounding a team’s performance.
A compelling story that contains inaccurate information can damage trust.
The same is true of entrepreneurs who promise more than their businesses can deliver.
Passion may explain why someone begins a project.
Competence helps establish whether that person can perform the work.
Execution determines whether the work consistently meets expectations.
For a sustainable business, all three can be valuable.
Work-Life Balance Is Also a Business Question
The debate’s discussion of work-life balance raised another important distinction: the difference between working more hours and producing greater value.
Entrepreneurs sometimes face periods when launching or expanding a business requires substantial personal sacrifice.
Developing services, acquiring customers, and managing operations may demand additional time, particularly when the business has limited resources.
But working longer does not automatically mean working more effectively.
An entrepreneur can spend extensive hours on activities that produce little measurable progress.
The more useful questions concern results.
Are those hours helping attract customers, improve service quality, strengthen financial performance, or develop a more efficient operation?
Or are they compensating for poor planning and unnecessary complexity?
Employees face a different set of considerations.
Many have limited control over scheduling, compensation, staffing, or organizational policies.
A worker’s ability to improve work-life balance may therefore depend partly on decisions made by an employer.
It would be misleading to treat employees and business owners as though they possess identical levels of control.
For organizations, sustainable performance requires examining workload, expectations, staffing, and operational efficiency.
For individuals, the challenge is understanding which decisions are within their control and which require changes at the organizational level.
Long hours may sometimes be necessary.
But hours alone are not a reliable measure of professional achievement.
The Real Challenge: Turning Knowledge Into Results
The Jubilee debate revealed how easily conversations about success can become arguments over individual attitudes rather than examinations of practical decisions.
One side may emphasize personal responsibility while underestimating economic barriers.
Another may emphasize structural disadvantages while giving insufficient attention to the decisions individuals and businesses can make within those constraints.
Neither approach provides a complete framework for entrepreneurship.
A business owner needs to understand the market, evaluate financial risks, develop useful skills, and identify opportunities that are realistic under existing conditions.
Technology can help with those responsibilities.
Experienced professionals can also provide valuable guidance.
But neither AI nor professional advice eliminates the entrepreneur’s obligation to make informed decisions.
The most effective approach is to combine available resources with independent judgment.
That includes recognizing when an AI-generated recommendation requires verification, when outside expertise is worth paying for, and when a business should reject an opportunity that does not fit its objectives.
It also means understanding that success may look different from one entrepreneur to another.
Not every business needs to become a national corporation or attract major investors.
For some owners, success may mean developing a profitable local operation, maintaining financial stability, serving a specialized market, or building an independent company that can operate sustainably over time.
Those objectives are no less legitimate simply because they differ from the ambitions of a high-profile investor.
Conclusion: When the Plan Meets Reality
A football team can enter a season with talented players, experienced coaches, sophisticated analytics, and an impressive playbook.
Those advantages may improve its competitive position.
But the team must still perform when the game begins.
Entrepreneurship presents a similar challenge.
A business owner may have an excellent business plan, access to artificial intelligence, experienced advisers, and financial backing.
None of those assets guarantees sustainable revenue.
Likewise, an entrepreneur beginning with limited resources should not assume that every opportunity is permanently out of reach.
The practical challenge is to understand the market, identify achievable objectives, develop relevant skills, and make decisions that improve the business over time.
Kevin O’Leary’s appearance on Jubilee Media offered a public examination of disagreements about wealth, work, and economic opportunity.
The value of that discussion is not determined by which participant delivered the most memorable response.
It lies in whether the arguments help people better understand the decisions they face.
Hard work matters, but circumstances influence opportunity.
Capital matters, but financing carries costs.
Passion matters, but customers expect competence.
Artificial intelligence matters, but its output requires judgment and verification.
For entrepreneurs, the challenge is not choosing one of those factors while dismissing the others.
It is understanding how they work together.
“Because in business, as in sports, a plan is only the beginning. The real test comes when that plan meets reality.”
Sources
– [Jubilee’s official episode listing]
– [BuzzFeed — Kevin O’Leary’s Jubilee Debate With Gen Z Workers Goes Viral]
– [The Daily Wire — Shark Tank Star Clashes With Gen Z Worker]
– [Congressional Research Service — Housing Cost Burdens in 2024]
– [Federal Reserve Banks — 2026 Report on Employer Firms]
Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.
Share this: