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.
Discover more from
Subscribe to get the latest posts sent to your email.
