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.
Measuring the Impact
By Cheval John | Vallano Media
This article was created with the assistance of artificial intelligence.
The final version was reviewed, edited and fact-checked by the author

Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.
One of the easiest claims to make about artificial intelligence is that it saves time.
That may be true.
But I wanted something better than a feeling.
I wanted evidence.
Not perfect evidence.
Not a controlled experiment.
Not a scientific study.
Just enough documentation to answer a practical question:
“What actually changed after I integrated AI into my work?”
That meant looking at time.
Output.
Workflow.
And the way I was spending my attention.
The answer turned out to be more complicated than simply saying:
“AI made me faster.”
It did make some parts faster.
But the bigger change was that I started working differently.
Before AI, Time Was Concentrated in Production
Before I built an AI-assisted workflow, producing an article meant I handled nearly every stage manually.
Research.
Organization.
Drafting.
Editing.
Rewriting.
Headline development.
Formatting.
Publishing.
For an article of more than 800 words, I could easily spend three to four hours moving from the idea to publication.
That number is not a controlled benchmark.
I was not timing every stage in those years.
Different articles required different amounts of research.
Some were easier than others.
Some involved interviews.
Some involved more complicated subjects.
So I cannot take a four-hour article from the past, compare it to a forty-minute article today and declare that AI made me six times more productive.
That would be cleaner than the evidence allows.
But the comparison is still useful.
My process used to require significantly more manual effort across nearly every stage.
Today, much of that effort has been redistributed.
I Started Measuring the Workflow
As I became more serious about AI integration, I started paying attention to production time.
Not because speed was the goal.
Because I wanted to know what was changing.
One of the earliest useful benchmarks came from this book.
The first day’s chapter took about “43 minutes” from the first draft through the publication-ready stage, excluding research that had already been done.
Later in the challenge, another chapter moved through the editorial process, locked manuscript, main graphic, tags and teaser in roughly “10 minutes.”
Those numbers are interesting.
They are also easy to misuse.
The chapters were different.
The research requirements were different.
I was becoming more familiar with the workflow.
The AI systems were operating within a structure I had already built.
And some of the improvement may have come from repetition and experience, not AI alone.
That matters.
I was not running a controlled experiment where every variable remained the same.
So I do not look at those numbers as proof of a specific productivity percentage.
I look at them as evidence of something more practical:
“The workflow was becoming easier to execute.”
The Indiana Article Gave Me Another Benchmark
A separate article gave me another useful data point.
The drafting-to-final stage took about “36 minutes and 54 seconds.”
Scheduling and production added roughly another “31 minutes.”
That matters because it shows why “writing time” alone can be misleading.
A finished article is not just a draft.
There is still production.
Formatting.
Graphics.
Scheduling.
Final checks.
Publishing infrastructure.
If I only measured the drafting stage, I could tell myself a much more impressive story.
But it would not represent the full work.
That became one of the lessons of tracking time:
“Measure the process you actually perform, not the piece that makes the best statistic.”
Faster Drafting Was Only Part of the Change
AI definitely reduced friction in drafting.
I no longer had to stare at a blank screen for as long.
I could start with research notes, identify the structure, build an outline and move into the draft faster.
But that was not the most important change.
The most important change was what I could do with the time that opened up.
I could challenge the argument.
I could check the claims.
I could go back to the sources.
I could run a truth pass.
I could red-team the story.
I could inspect the graphic.
I could compare versions.
I could spend more time deciding whether something should survive rather than spending all my time trying to produce the first version.
That is a different kind of productivity.
Output Increased Because Friction Decreased
Another change was output.
Once the workflow became repeatable, I could produce more without feeling as if every article had to begin from zero.
Research had a process.
Drafting had a process.
Verification had a process.
Editing had a process.
Graphics had a process.
Publishing had a process.
The result was not simply that AI could generate text faster.
The result was that I was building a publishing system.
That distinction matters.
A faster writer can produce more words.
A better system can produce more finished work.
Those are not the same thing.
More Output Does Not Automatically Mean Better Work
There is a danger here.
Once production becomes easier, it is tempting to produce simply because you can.
Another article.
Another post.
Another graphic.
Another idea.
AI can make quantity feel almost effortless.
But volume is not the same as value.
If the additional output is poorly researched, repetitive or unnecessary, then more productivity may just mean more noise.
And more capacity is only useful if I choose what deserves that capacity.
That is why I do not want to measure success by article count alone.
The better question is whether the additional capacity allows me to produce work that is:
more consistent,
better verified,
more useful,
more complete,
or more sustainable.
If the answer is no, then the increased output is not much of an achievement.
AI Changed My Role
There was another change that was harder to measure with a stopwatch.
My role changed.
Earlier, I was doing nearly every task myself.
Now I increasingly direct the tasks.
I decide what needs research.
I decide what needs verification.
I decide when AI should challenge the work.
I decide what version survives.
I decide when the manuscript is locked.
I decide when the graphic is ready.
I decide what gets published.
That does not mean I stopped working.
It means the work moved upward.
More of my effort went into coordination, judgment and approval.
I became less focused on executing every individual task manually and more focused on managing the system that produced the work.
That is one of the biggest changes AI created for me.
And it is difficult to express with a simple productivity number.
The Work Became More Repeatable
Before the workflow existed, every article depended more heavily on memory.
Did I check that number?
Did I verify that quote?
Did I review the headline?
Did I challenge the argument?
The more tasks I handled manually, the easier it was for the process to vary from article to article.
Now the workflow gives me checkpoints.
That does not guarantee quality.
But it creates consistency.
I know what happens after the draft.
I know what happens after verification.
I know when the red-team pass begins.
I know when the manuscript becomes locked.
That repeatability matters because publishing regularly requires more than creativity.
It requires a system that can work again tomorrow.
Some Work Actually Increased
AI did not make every part of journalism faster.
In some areas, it created additional work.
AI output has to be checked.
Sources have to be verified.
Rewritten sentences have to be compared against the evidence.
Graphics have to be inspected.
Generated suggestions have to be evaluated.
A polished AI answer can deserve extra scrutiny because fluency can make a weak or false claim look settled.
So there are moments when AI saves time in one part of the process and adds work somewhere else.
Sometimes AI does not remove time from the process.
It moves the time somewhere else.
That is not necessarily a problem.
The important question is whether those additional minutes improve the final work.
If they do, then the effort may be valuable.
The Fast Workflow Was Not Built Overnight
There is another part of the productivity story that is easy to miss.
The workflow I use today did not appear instantly.
It sits on top of months of learning.
Experimentation.
Failed prompts.
Revisions.
New workflows.
Abandoned ideas.
Understanding what AI does well.
And understanding where I do not trust it.
The current efficiency exists partly because of that earlier investment.
Someone starting from zero should not expect to reproduce my current workflow speed immediately.
The faster process came after building the system.
That setup time counts too.
Failed Attempts Count
There is another temptation when measuring productivity:
Remember the successes.
Forget the failures.
A graphic that works on the first generation is easy to count.
The five bad versions before the final one are easy to forget.
A clean draft looks efficient.
The abandoned structure that came before it can disappear from the measurement.
If I want an honest record, I have to include rework.
Failed experiments.
Bad outputs.
Wrong directions.
The things that did not survive.
A fair measurement system cannot count only the examples that went smoothly.
The failures are part of the cost of the workflow too.
Efficiency Is Not the Same as Cutting Corners
This distinction has become increasingly important to me.
Efficiency means removing unnecessary friction.
Cutting corners means removing necessary safeguards.
Those two things can look similar from the outside.
Both may reduce time.
But they produce very different results.
If AI helps me organize notes faster, that is efficiency.
If I stop reading the source because AI summarized it, that is cutting a corner.
If AI helps identify weak claims before publication, that is efficiency.
If I accept its factual corrections without checking them, that is cutting a corner.
The goal is not to make every stage shorter.
The goal is to make the whole process better.
Time Saved Needs Somewhere to Go
This may be the most important measurement question of all.
What happens to the time AI saves?
If I save thirty minutes and immediately fill those thirty minutes with more low-value work, I have increased activity.
Not necessarily productivity.
If I use the time to verify a source, improve the argument, learn a new skill, work on another important project or simply reduce unnecessary workload, then the savings become meaningful.
AI does not decide where the time goes.
I do.
That makes time savings a management question as much as a technology question.
The Numbers Need Context
I have started collecting timing benchmarks because I want a record.
But the numbers need context.
A ten-minute workflow does not mean every chapter should take ten minutes.
A forty-minute article is not automatically better than a three-hour article.
A fast result may reflect:
better preparation,
a familiar subject,
stronger systems,
less research,
greater experience,
or a simpler assignment.
A slower result may reflect deeper reporting or more complicated evidence.
And the examples I track are not automatically representative of every kind of journalism I produce.
An interview-heavy story may require a completely different amount of time.
So might an unfamiliar subject.
A breaking story.
Or a piece that requires deeper original reporting.
That is why I do not want to turn speed into the standard.
The numbers are signals.
They help me see how the system is changing.
They do not tell the whole story.
Measuring Speed Can Change the Work
There is another complication.
The moment I start measuring speed, I also have to watch whether the measurement itself is changing how I work.
If I know the clock is running, do I rush?
Do I become reluctant to go back to research because it will hurt the number?
Do I treat a ten-minute workflow as something I need to beat?
That would defeat the purpose.
The measurement is supposed to help me understand the workflow.
The workflow should not start serving the measurement.
If the story needs more time, it gets more time.
Quality Is Harder to Measure
Time is easy to measure.
Quality is not.
I can tell you that a process took forty minutes.
It is much harder to reduce the quality of the finished journalism to a single number.
Did I use stronger sources?
Did I catch an error before publication?
Did important context survive the editing process?
Did the headline accurately represent the reporting?
Did the workflow make my work more consistent?
Did I reduce avoidable corrections?
Those questions may ultimately matter more than the stopwatch.
That means any serious measurement of AI-assisted journalism needs more than productivity statistics.
It needs evidence about the quality of the work too.
The Better Measurement May Be Capacity
The more I have worked this way, the more I think the real benefit may be capacity.
How much high-quality work can I responsibly manage?
How many different projects can I keep moving?
How quickly can I move from research to publication without losing oversight?
How much attention remains available for the decisions that actually require me?
That is different from measuring words per hour.
Capacity includes time.
But it also includes cognitive load.
Consistency.
Repeatability.
Quality control.
And the ability to keep operating without every project becoming exhausting.
Capacity may be the most important benefit I see right now.
Future measurements may show that consistency, quality control or reduced cognitive load matter even more.
That is why I want to keep measuring.
Measuring the Wrong Thing Can Create the Wrong Incentive
Metrics influence behavior.
If I only measure production time, I will naturally try to make everything faster.
If I only measure output, I will try to publish more.
If I only measure traffic, I may start choosing stories based on clicks.
That is why measurement needs to reflect the kind of journalism I actually want to produce.
Some useful questions might be:
Did I verify the central claims?
Did the story survive the red-team pass?
Did I catch problems before publication?
Did the workflow reduce unnecessary repetition?
Did the finished work meet the standard?
Did the process become easier to repeat?
Those questions are less exciting than saying AI made me five times faster.
They are also more useful.
Efficiency Has a Cost Side
AI-assisted work is not free simply because it saves time.
There are tools.
Subscriptions.
Training.
Experimentation.
Failed generations.
And the time required to build and manage the system.
Those costs matter too.
A productivity measurement that counts only minutes saved and ignores what it took to create those savings is incomplete.
The goal is not to prove that the technology has no cost.
The goal is to understand whether the total system gives me enough value to justify it.
I Am Still Building the Dataset
This is not the final measurement.
I am still early in the process.
The timing records from this writing challenge are part of a larger dataset I am building around my own work.
More articles will give me better comparisons.
More mistakes will show which safeguards need improvement.
More repetition will show whether the gains are durable or just the result of novelty.
And a better record will help me distinguish what came from AI from what came from experience, repetition and improved systems.
That is how I want to approach AI productivity.
Not with one impressive example.
With a record.
What Changed?
So what changed after integrating AI?
I became faster in parts of the workflow.
I increased the amount of work I could manage.
The process became more structured.
The work became more repeatable.
More of my attention shifted from producing the first version to reviewing, challenging and directing the work.
Some tasks became easier.
Some verification work increased.
Some time disappeared.
Some time simply moved.
And my role changed from doing every task manually to managing a system of tasks.
That is more difficult to fit into a marketing slogan.
But it is closer to what actually happened.
AI did not simply make me faster.
It changed how I work.
And I am still measuring exactly what that change means.
Because the real question is not:
“How much faster can I publish?”
It is:
“What can I do better with the time, attention and capacity AI gives back?”

Graphics created with AI-assisted design tools.
Visual concepts, editorial direction, composition, and final creative decisions were developed by Vallano Media.
Sam Houston Holds Off Pepperdine 85–77 as Free Throws Prove Decisive
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 had built a 15-point second-half lead against Pepperdine, but with just over three minutes remaining Wednesday night, the Bearkats found themselves facing a much more difficult finish than the scoreboard had suggested earlier.
Pepperdine had reduced the deficit to 67–63 with 3:30 remaining.
Moments later, a layup brought the Waves within two points.
What followed was not an offensive explosion from the field.
Instead, Sam Houston relied on free-throw shooting to preserve an 85–77 victory at Bernard G. Johnson Coliseum.
The Bearkats finished 34 of 38 from the free-throw line, an 89.5% performance that helped overcome inconsistent shooting from the field.
Jacobe Coleman and Aidan McDowell led Sam Houston with 20 points apiece.
Yoda Oke added 14 points and eight rebounds, while Justin Begg contributed 13 points and five rebounds.
The victory demonstrated both Sam Houston’s ability to respond under pressure and the areas that will require improvement as the season progresses.
A First-Half Rally Changes the Momentum
Pepperdine appeared to be gaining control late in the opening half, forcing Sam Houston to respond before halftime.
The Bearkats answered with a decisive offensive stretch.
McDowell connected from three-point range, while Oke contributed inside as Sam Houston worked its way back into the contest.
The Bearkats continued building momentum during the closing minutes.
McDowell delivered the final basket, hitting a three-pointer at the buzzer to send Sam Houston into halftime with a 41–35 lead.
The sequence transformed the complexion of the game.
Instead of entering the locker room trailing, Sam Houston had established a six-point advantage and carried that momentum into the second half.
A Comfortable Lead Becomes a Battle
Sam Houston extended its advantage after halftime, eventually moving ahead 51–36.
The 15-point margin suggested the Bearkats might be approaching a comfortable victory.
Pepperdine had other ideas.
The Waves responded with a 7–0 run, forcing Sam Houston to regain its offensive rhythm.
Coleman helped stop the momentum with a turnaround jumper, while Zion Pipkin added free throws to restore a double-digit advantage.
One of the game’s more memorable sequences came when Begg recorded a steal that eventually led to an alley-oop dunk by Enel St. Bernard, assisted by Pipkin.
The play provided an energetic moment for the Bearkats, but it did not end Pepperdine’s resistance.
The Waves continued attacking, gradually reducing the deficit.
With 3:58 remaining, Pepperdine connected on a three-pointer to cut Sam Houston’s lead to 65–63.
Pipkin answered with a basket to make it 67–63 with 3:30 remaining.
But Pepperdine responded again.
Alex Constanza converted a layup with 3:14 left, reducing the deficit to 67–65.
A game that had appeared under control had become a one-possession contest, leaving Sam Houston little room for mistakes.
The Bearkats’ response would determine the outcome.
Free Throws Become the Difference
Sam Houston did not need a series of three-pointers or spectacular field goals to regain control.
It needed to make its free throws.
Oke converted three consecutive attempts to extend the Bearkats’ advantage to 70–65.
Coleman later made three free throws after being fouled on a three-point attempt, pushing the lead to 73–65 with 2:06 remaining.
Additional free throws from St. Bernard and McDowell helped restore a double-digit margin.
After Pepperdine pulled within two, Sam Houston scored its next eight points from the free-throw line, rebuilding a 75–65 advantage.
The Waves continued scoring during the final minute, but the Bearkats consistently answered at the line.
Coleman, McDowell and Begg converted additional free throws in the closing seconds to secure the eight-point victory.
The final statistics revealed just how important those opportunities had been.
Sam Houston made 23 field goals and connected on only five of 20 three-point attempts, a 25% performance from beyond the arc.
Its second-half shooting was particularly revealing.
The Bearkats made just eight field goals after halftime and missed all five of their three-point attempts.
Yet Sam Houston still scored 44 second-half points.
Of those 44 points, 28 came from the free-throw line.
The team finished 28 of 32 on second-half free throws, converting 87.5% of its attempts.
That production became the defining statistical difference.
Pepperdine made 10 three-pointers compared with Sam Houston’s five, but the Waves converted only 15 of 27 free throws.
Sam Houston’s ability to capitalize on its opportunities at the line helped offset Pepperdine’s advantage from beyond the arc.
Contributions Beyond the Leading Scorers
Although Coleman and McDowell led the Bearkats offensively, Sam Houston received contributions from several players.
Oke’s 14 points and eight rebounds provided an important presence, particularly during the second half.
Begg added 13 points, five rebounds and two assists, contributing to the team’s offensive production despite struggling with his field-goal shooting.
St. Bernard finished with seven points and nine rebounds, while Pipkin contributed seven points.
Riccardo Greppi added four points and six rebounds.
Those contributions were significant during a game in which Sam Houston needed scoring opportunities beyond its perimeter shooting.
The Bearkats’ ability to draw fouls and convert their opportunities became particularly valuable as Pepperdine reduced the lead.
The performance also illustrated the importance of finding different ways to score when an offense struggles to establish a consistent rhythm.
A Victory With Lessons Before Illinois
Sam Houston’s victory over Pepperdine demonstrated that the Bearkats could respond when a substantial lead began slipping away.
The first-half rally showed their ability to change momentum quickly.
Their ability to draw fouls and convert free throws allowed them to withstand Pepperdine’s late challenge.
But the victory also exposed weaknesses.
The Bearkats struggled from three-point range, failed to make a second-half three-pointer and allowed a 15-point advantage to shrink to two.
Those are areas that could become more consequential against stronger opposition.
Sam Houston’s next challenge comes Friday against No. 3 Illinois at State Farm Center in Champaign.
The Pepperdine game provided an early example of how the Bearkats can find ways to win without consistently shooting well.
Against Illinois, maintaining offensive rhythm and limiting extended scoring droughts could be considerably more important.
For now, Sam Houston can take satisfaction in an 85–77 victory that required composure in the closing minutes.
