Archive | November 2026

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.

Western Kentucky Overpowers Sam Houston, Completes Perfect Conference USA Volleyball Season

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.

Sam Houston opened its final regular-season volleyball series with a 25–23 first-set victory over Western Kentucky on Thursday, November 12, at Bernard G. Johnson Coliseum in Huntsville, Texas.

For a moment, the Bearkats had put the Conference USA leaders in an unfamiliar position.

Western Kentucky’s response demonstrated why the Hilltoppers have remained the conference’s standard-bearer.

The visitors won the next six sets across two matches, defeating Sam Houston 3–1 Thursday before completing a straight-set sweep Friday afternoon.

The results gave Western Kentucky a 22–6 overall record, a perfect 16–0 mark in Conference USA and a 17-match winning streak entering the conference tournament.

Sam Houston finished its regular season 17–12 overall and 8–8 in conference play, having already secured a postseason berth.

While the Bearkats showed they could compete with Western Kentucky early in the series, the Hilltoppers’ blocking, offensive efficiency and sustained scoring runs ultimately determined the outcome.

Thursday: Western Kentucky Takes Control at the Net

Sam Houston began Thursday’s match with one of its strongest offensive sets of the weekend.

The Bearkats recorded 16 kills in the opening frame, compared with nine for Western Kentucky, and rallied to win 25–23 after trailing 23–22.

However, the momentum did not carry into the remaining sets.

Western Kentucky responded with victories of 25–20, 25–11 and 25–10, increasingly controlling play at the net.

The second set provided an early indication of the challenge facing Sam Houston.

With Western Kentucky leading 8–7, Alivia Skidmore helped spark a six-point run that extended the advantage to 14–7.

The Bearkats later closed within three points at 20–17, but the Hilltoppers finished the set to even the match.

Western Kentucky’s blocking became even more effective in the third set.

After building a 10–7 lead, the Hilltoppers extended their advantage to 16–8 and eventually 23–9.

They recorded 13 kills and hit .481 in the frame while limiting Sam Houston to four kills.

The fourth set was more decisive.

Western Kentucky opened with five consecutive points, established a 12–2 lead and continued pulling away.

The Hilltoppers hit .611 in the final set, recording 12 kills on 18 attempts without an attack error.

For the match, Western Kentucky hit .345 with 48 kills and nine attack errors.

Sam Houston finished with 38 kills, 33 errors and a .039 hitting percentage.

The largest statistical difference came at the net, where Western Kentucky recorded 16 blocks to Sam Houston’s two.

Senior Izzy Van De Wiele led the Hilltoppers with a career-high 11 blocks, while Kaira Knox recorded 16 kills and five blocks.

Skidmore added 12 kills, and Faith Young contributed 10.

Chloe Monson led Sam Houston with 12 kills.

Chelsea Butler finished with seven, while Faith Roulston and Bella Wood recorded six apiece.

Shaelin White contributed 14 digs.

Western Kentucky’s defensive pressure was particularly noticeable against Butler, one of Sam Houston’s most efficient attackers throughout the season.

As the match progressed, the Hilltoppers repeatedly challenged attacks at the net, limiting Sam Houston’s ability to establish a consistent offensive rhythm.

Western Kentucky head coach Travis Hudson credited Van De Wiele’s blocking for disrupting the Bearkats’ approach.

“She just completely took them out of what they were doing in that third set. They even spun their lineup to get different matchups in the fourth,” Hudson said.

Hudson also described Van De Wiele’s performance as unusually dominant, even by her standards.

The blocking performance helped turn a competitive opening into a convincing four-set victory.

Friday: Hilltoppers Finish the Regular Season Unbeaten

Sam Houston entered Friday’s rematch seeking a different result, but Western Kentucky quickly established control.

The Hilltoppers won 25–18, 25–16 and 25–8 to complete the series sweep.

The opening set was competitive early, with the teams tied at seven.

Western Kentucky gradually created separation through its offense and service game.

Sam Houston remained within reach during portions of the set, including a four-point scoring run that forced a Western Kentucky timeout, but the Hilltoppers closed out the frame.

Western Kentucky opened the second set with three consecutive points and extended its lead to 7–1.

The Bearkats struggled to recover.

The Hilltoppers recorded 12 kills and hit .333 in the set, while Sam Houston finished with eight kills and a .000 hitting percentage.

Western Kentucky claimed the frame 25–16, moving within one set of an undefeated conference regular season.

The third set produced the most lopsided result of the weekend.

After the teams were tied at seven, Western Kentucky took control and allowed Sam Houston just one additional point.

The Hilltoppers won 25–8, recording 14 kills and hitting .591 in the final set.

Sam Houston managed four kills.

Across Friday’s match, Western Kentucky recorded 36 kills, seven attack errors and a .387 hitting percentage.

Sam Houston finished with 24 kills and 23 errors on 84 attempts, producing a season-low .012 hitting percentage.

Western Kentucky also recorded nine service aces and seven blocks.

Van De Wiele delivered another efficient performance, finishing with eight kills on nine attempts without an attack error.

Her .889 hitting percentage established a career best, and she added five blocks.

Young also recorded eight kills.

Setter Kate Rush contributed 31 assists and four service aces, while Knox added seven kills and four aces.

Monson led Sam Houston with seven kills.

Butler finished with five, and Roulston added four.

Brenlin Garlitz recorded 10 assists, while White contributed six digs.

Friday’s result completed Western Kentucky’s undefeated conference campaign and extended its winning streak to 17 matches.

The Numbers Behind Western Kentucky’s Advantage

The two matches highlighted a substantial difference in execution, particularly in attacking efficiency and blocking.

Western Kentucky combined for 84 kills across the series, compared with 62 for Sam Houston.

The Hilltoppers also outblocked the Bearkats 23–6 over the two matches.

Those differences were significant against a Sam Houston team that had produced several strong individual performances throughout the regular season.

According to Conference USA’s overall-season statistics through November 13, Monson ranked second in the league with 3.49 kills per set, totaling 380 kills in 109 sets.

Butler ranked 10th in hitting percentage at .315, while Rachelle Reed stood third in blocks per set at 1.15.

White led the conference in digs per set at 4.34, totaling 473 digs.

Sam Houston also ranked first in the conference in opponent hitting percentage at .185 and fourth in blocks per set at 2.21.

Those figures demonstrate that the Bearkats possessed legitimate defensive strengths and productive individual performers despite their difficulties against Western Kentucky.

However, the Hilltoppers entered postseason play with the conference’s leading hitting percentage at .298, along with league-leading averages of 2.33 blocks and 2.12 service aces per set.

The series illustrated how those strengths could work together.

Western Kentucky’s blocking disrupted Sam Houston’s attack, while the Hilltoppers’ offensive efficiency and serving helped generate sustained scoring runs.

The result was not simply a difference in individual talent, but a clear difference in team execution over the final six sets.

Two Coaches, More Than 1,600 Career Victories

The series also featured two of the conference’s most accomplished coaches.

Western Kentucky’s Travis Hudson reached 800 career victories in November 2025, while Sam Houston’s Brenda Gray earned her 800th victory on October 16, 2026, against Delaware.

Both have built long-running programs, although their teams entered the final regular-season weekend with different circumstances.

Western Kentucky was pursuing another undefeated conference season.

Sam Houston, selected last in the Conference USA preseason poll, had already exceeded that expectation by securing a tournament berth and reaching 17 regular-season victories.

The Hilltoppers’ success reflects a sustained period of conference dominance.

Western Kentucky has completed eight undefeated Conference USA regular seasons since joining the league in 2014, including seven of the past eight seasons.

Friday’s victory added another chapter to that record.

“I feel like we’re playing our best volleyball at the end,” Hudson said following Friday’s sweep.

His assessment reflected a weekend in which Western Kentucky responded to an opening-set defeat by winning six consecutive sets, including four by double-digit margins.

Sam Houston Looks Toward the Postseason

Although the final weekend ended with two losses, Sam Houston’s season continues.

The Bearkats finished 17–12 overall and 8–8 in Conference USA, earning a place in the conference tournament after being picked last in the preseason standings.

That accomplishment should not be overlooked.

At the same time, the Western Kentucky series exposed the difficulty Sam Houston encountered when facing a team capable of combining strong blocking with efficient offense.

The Bearkats’ challenge entering the postseason will be to generate more consistent attacking opportunities and avoid the extended scoring runs that proved costly during the series.

Western Kentucky enters the tournament as the No. 1 seed and host, carrying an undefeated conference record and considerable momentum.

The Conference USA Tournament will take place November 20–22 at E.A. Diddle Arena in Bowling Green, Kentucky.

For Western Kentucky, the regular season ended with another conference milestone.

For Sam Houston, the weekend provided a difficult final test before postseason competition.

The Bearkats showed their potential by winning Thursday’s opening set.

The Hilltoppers demonstrated their strength by winning everything that followed.


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

The Human in 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.

AI can do a lot.

It can assist with research.

Summarize.

Organize.

Draft.

Edit.

Compare.

Challenge.

Generate ideas.

Suggest headlines.

Help build graphics.

Help prepare material for publication.

But there is still a question underneath all of that:

“Who is making the decisions?”

That question matters more to me than how advanced the technology becomes.

Because the more capable AI gets, the easier it becomes to confuse assistance with authority.

I do not want that confusion inside my workflow.

AI can help me move faster.

It can help me see more.

It can help me test the work.

But the decisions that determine what I publish still belong to me.

This Is Bigger Than Being “In the Loop”

Earlier in this book, I wrote about the importance of keeping a human in the loop.

That still matters.

But simply being present is not enough.

I can technically be part of the process while allowing AI to make most of the meaningful decisions.

I can click approve without really reviewing.

I can accept a rewrite because it sounds better.

I can use a suggested headline without checking whether it matches the evidence.

I can publish a graphic because it looks polished.

I can follow a recommendation because the AI sounds confident.

That is human presence.

It is not necessarily human control.

The question I care about now is:

“Where does the authority sit?”

And there is another question behind it:

“Is that authority real?”

Assistance and Authority Are Different

This distinction has become one of the most important parts of my workflow.

AI can assist with a decision.

That does not mean AI owns the decision.

For example, I can ask AI to compare three possible headlines.

It can tell me which one appears clearer.

It can identify which one may overstate the story.

It can suggest alternatives.

That is assistance.

But I still decide which headline gets published.

I can ask AI whether a paragraph seems weak.

It can point out missing context.

It can challenge the reasoning.

It can suggest a rewrite.

That is assistance.

But I still decide whether the paragraph survives.

The same principle applies throughout the workflow.

AI can contribute.

I retain authority.

But keeping authority human only matters if I am still exercising independent judgment.

If I approve whatever the system recommends, the authority exists mostly on paper.

I Have to Know What I Am Delegating

The more AI becomes integrated into my work, the more important it is to know what I am actually handing over.

Some delegation is obvious.

“Summarize these notes.”

“Create three headline options.”

“Find the weak point in this argument.”

“Clean up the grammar.”

Other delegation is less obvious.

“Which fact matters most?”

“What should lead the story?”

“Which source is more credible?”

“Is this ready to publish?”

Those questions carry more editorial judgment.

They may look like ordinary prompts.

But they can quietly transfer decision-making influence.

That does not mean I can never ask them.

It means I need to understand what I am asking AI to do.

I can use its response as input.

I should not confuse that input with the final decision.

A Tool Can Shape the Decision Before I Make It

This is one of the subtler problems.

AI does not need to make the final decision to influence it.

If a system chooses which sources I see first, that matters.

If it ranks one piece of evidence above another, that matters.

If it proposes the structure of the story, that matters.

If it gives me three headline choices, it has already influenced the range of options I am considering.

The final click may still belong to me.

But the tool may have shaped the decision long before I reach that point.

That means human control cannot exist only at the end.

I need to pay attention to how the workflow is shaping what I see, what I consider and what I ignore.

Not Every Decision Has the Same Weight

Some decisions are low risk.

Should this sentence be shorter?

Should this paragraph move higher?

Does this headline need fewer words?

Other decisions carry much more weight.

Is this source trustworthy?

Does the evidence support the accusation?

Does this wording imply causation?

Is this person being treated fairly?

Does this story need another source before publication?

Should this information be published at all?

The higher the consequence, the less comfortable I am with automatic delegation.

That is one reason I do not think a single rule works for every use of AI.

The level of human involvement should match the importance of the decision.

The stakes matter.

Human Judgment Does Not Mean Human Perfection

There is another point I have to acknowledge.

Humans make mistakes too.

I can misread a source.

I can become attached to an argument.

I can overlook context.

I can write a bad headline.

I can approve the wrong graphic.

I have biases.

I can be inconsistent.

Keeping the decision human does not magically make the decision correct.

Human authority does not make the judgment neutral.

It makes the judgment accountable.

Someone still has to be able to explain:

Why did you publish this?

Why did you trust this source?

Why did you use this wording?

Why did you leave this out?

Why did you believe the evidence was strong enough?

AI cannot carry that responsibility for me.

Authority May Be Shared

My workflow is built around the decisions I make.

But that does not mean editorial authority always belongs to one person.

In a larger newsroom, responsibility may be distributed.

A reporter may make one decision.

An editor another.

A producer may control part of the presentation.

A standards team may become involved.

A lawyer may review a particularly sensitive story.

The exact structure can change.

The principle does not.

Somebody needs meaningful authority over the consequential decisions.

And the people exercising that authority need enough understanding to evaluate what the system is producing.

The Most Important Decisions Often Happen Between the Steps

A workflow makes the process visible.

Research.

Draft.

Verify.

Red-team.

Edit.

Quality control.

Publish.

But some of the most important decisions happen between those labels.

Do I need more reporting?

Do I trust this explanation?

Is this technically true but misleading?

Am I forcing the story into a cleaner conclusion than the evidence supports?

Is the headline becoming stronger than the article?

Does this quote change the meaning?

Should I stop?

Those questions are harder to automate reliably because they depend heavily on context, judgment and consequences.

Sometimes they depend on experience.

Sometimes ethics.

Sometimes simply noticing that something does not feel settled yet.

That is where the human in the workflow matters most.

AI Can Recommend. I Can Reject.

One of the most important things I have learned is that I do not need to accept a useful-looking AI recommendation.

That sounds obvious.

In practice, it matters.

AI can give me a polished answer quickly.

That creates momentum.

The easiest thing is to keep moving.

Accept.

Insert.

Publish.

But I have found that some of the best decisions happen when I say:

No.

That headline is too strong.

That sentence does not sound like me.

That criticism is irrelevant.

That graphic is wrong.

That source is not good enough.

That conclusion goes beyond the evidence.

That draft needs more work.

The ability to reject AI is just as important as the ability to use it.

Familiarity Can Reduce Skepticism

There is another risk.

The more often a system gives me useful answers, the easier it becomes to trust the next answer.

That is understandable.

It is also dangerous.

Reliability can create habit.

Habit can reduce scrutiny.

The more often a system is right, the easier it becomes to stop questioning it.

That is exactly when skepticism still matters.

I do not need to assume every answer is wrong.

But I should not allow a good track record to turn into automatic approval.

Sometimes the Best Decision Is to Stop the Workflow

Efficiency can create pressure to keep going.

Once research becomes a draft, the draft becomes an edit, the edit becomes a graphic and the graphic becomes a scheduled post, the process starts building momentum.

That momentum can be useful.

It can also be dangerous.

There needs to be a point where I can stop everything.

Not delay publication by five minutes.

Stop it.

Go back.

Report more.

Change the premise.

Abandon the story if necessary.

A workflow is only genuinely under human control if the human can interrupt it.

Otherwise, the workflow is just moving toward publication.

But even that is not enough.

Authority is meaningful only when the surrounding system allows the human to use it.

If deadlines, incentives, workplace pressure or culture make “stop” impossible in practice, then formal authority may not mean much.

AI Can Make the Wrong Decision Look Reasonable

This is one of the reasons I remain careful.

A weak human idea often looks weak.

A half-developed thought may be obviously unfinished.

AI can make that same idea look polished.

It can organize it.

Strengthen the wording.

Add transitions.

Make the logic feel smooth.

That creates a dangerous possibility:

The presentation improves while the underlying decision remains bad.

A polished recommendation is still a recommendation.

A confident explanation is still something that needs evaluation.

Good language does not turn weak judgment into strong judgment.

The Human Decides What Matters

AI can find patterns.

It can rank information.

It can summarize what appears frequently.

It can identify what looks unusual.

But journalism still requires someone to decide what matters.

That is not always the same as what is most dramatic.

Or most popular.

Or most repeated.

Or easiest to summarize.

Something can be statistically unusual and editorially unimportant.

Something can receive little attention and still matter enormously.

Something can be interesting without being relevant.

Something can be true without belonging in the story.

Those are editorial decisions.

The technology can inform them.

It should not silently make them.

And human authority does not guarantee that I will make the right choice.

It means I am responsible for making and defending that choice.

The Human Decides What the Evidence Means

Evidence does not always explain itself.

Two sources may disagree.

A statistic may look important until the denominator changes the picture.

A quote may sound powerful until the surrounding context changes its meaning.

A trend may exist without showing causation.

AI can help surface those problems.

But the final interpretation still requires judgment.

Human judgment does not mean inventing meaning.

It means deciding what conclusions the evidence can actually support.

What does the evidence show?

What remains uncertain?

What can I say confidently?

What needs qualification?

Those decisions determine whether the journalism is careful or careless.

The Human Decides What Does Not Get Published

This may be even more important than deciding what gets included.

Every story leaves something out.

Some information is irrelevant.

Some is weakly supported.

Some is repetitive.

Some is potentially harmful.

Some cannot be verified.

Some may be interesting but unfair to include.

AI can suggest what belongs in the story.

But restraint is part of journalism too.

The ability to leave something out can be as important as the ability to find it.

There is a balance here.

Caution should not become an excuse to avoid publishing well-supported reporting.

Restraint matters.

So does having enough confidence to publish when the evidence is strong.

The Human Owns the Exceptions

Workflows are built around patterns.

Most articles move through familiar stages.

Most fact checks follow familiar logic.

Most edits involve familiar questions.

But unusual situations happen.

A source contradicts the official record.

A new document arrives after the draft is finished.

A quote changes the central premise.

A graphic creates a meaning I did not intend.

A legal or ethical question appears late.

The workflow cannot predict every exception.

That is where judgment becomes more important, not less.

A good system helps me handle routine work.

It should also leave enough flexibility for me to recognize when the routine no longer applies.

This Changes How I Think About Automation

I am interested in automation.

I am interested in AI agents.

I am interested in systems that can monitor information, organize work and reduce repetitive tasks.

But the more I think about automation, the more I separate two things:

“execution” and “authority.”

I am comfortable automating parts of execution.

Monitoring.

Sorting.

Formatting.

Collecting.

Comparing.

Preparing.

Flagging.

I am much more careful about automating authority.

What is true?

What is fair?

What is strong enough to publish?

What deserves emphasis?

What should be excluded?

When should the process stop?

Those are different kinds of questions.

The Better the AI Gets, the More Important This Becomes

It might seem that better AI would reduce the need for human involvement.

In some tasks, it probably will.

But greater capability also means greater temptation to delegate.

If AI becomes better at research, drafting, editing, graphics and production, the question will not simply be:

Can it do this?

The question will become:

Should I let it decide this?

Those are not the same question.

Capability does not automatically create authority.

A system can be very good at producing an answer while still being the wrong place to locate responsibility.

My Job Is Becoming More About Decisions

This has been one of the biggest changes in my own work.

The more AI assists with execution, the more valuable my judgment becomes.

I am spending less of my attention on:

How do I physically produce every part of this?

And more on:

Is this right?

Is this useful?

Is this supported?

Is this fair?

Does this belong?

What needs another look?

What should happen next?

That is not less work.

It is different work.

And in many ways, it is closer to what I should have been concentrating on all along.

I Still Have to Know the Craft

There is a catch.

I cannot reliably direct work I do not understand.

If I do not understand reporting, I cannot reliably judge the research.

If I do not understand sourcing, I cannot evaluate the evidence.

If I do not understand writing, I cannot recognize a weak draft.

If I do not understand editing, I cannot know when meaning has changed.

If I do not understand visual communication, I may approve a misleading graphic.

AI can help people learn the craft.

But the more consequential the decision, the more dangerous it becomes to rely on a tool I cannot evaluate.

AI does not eliminate the need to know the craft.

It may make that knowledge even more important.

Because now I am not only doing the work.

I am evaluating work produced with assistance.

Direction Requires Standards

To direct AI well, I need standards.

What counts as a strong source?

What level of verification is enough?

What tone fits the publication?

What kinds of claims require more scrutiny?

What makes a graphic acceptable?

What does publication-ready mean?

Without standards, AI can produce endless options.

But options are not direction.

The human brings the standard.

The standard makes the decisions possible.

But standards need review too.

A consistent process can still produce consistently bad decisions if the standard itself is weak.

The workflow should not only test the work.

Over time, it should also force me to test the standards behind the work.

The Human in the Workflow Is Not a Symbol

I do not want the human role to become ceremonial.

Not a name at the end of the process.

Not a final click.

Not someone who approves whatever the system produces.

The human role has to exist throughout the workflow.

Setting the goal.

Testing the claims.

Rejecting bad recommendations.

Recognizing uncertainty.

Stopping the process when necessary.

Owning what gets published.

That is meaningful control.

Real authority means having decision space throughout the process.

Not just possession of the publish button.

AI Can Do a Lot

And I expect it will be able to do even more.

That does not bother me.

The goal is not to protect tasks simply because humans used to perform them.

If AI can handle something safely, accurately and efficiently, I want to understand how to use that capability.

But I also want to know where I draw the line.

Not because humans must perform every task.

Because somebody still has to make the decisions that carry responsibility.

For my work, that somebody is me.

AI can assist with research.

Draft.

Assist with verification.

Challenge.

Edit.

Organize.

Prepare.

Recommend.

But contribution is not authority.

And formal authority is not enough if I cannot exercise it independently.

The most important decisions still belong to me:

evidence,

fairness,

meaning,

uncertainty,

restraint,

publication,

responsibility.

And the more capable the technology becomes, the more deliberate I have to be about keeping those decisions genuinely human.


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