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.