Automation should leave a trail

A useful workflow is not a magic trick. It should show what happened, what it used, and where a person still needs to decide.

By Updated 2 min read

Automation is usually judged by how much human work it removes. That is too narrow. A good automation does more than run a task. It makes the process faster while keeping the inputs, the decisions, the changes and the outcome clear.

A document comes in. A workflow processes it. Something comes out. You should be able to see what the system received, what it did, what it changed, and whether a person still needs to review the result.

Invisible is not the same as trustworthy

When a workflow produces an output but gives you no way to see how it got there, problems become hard to find.

You may not know which source it used, which rules it followed, what the model changed, whether a step failed, or whether the result ever reached the person it was meant for.

This matters even more when AI is involved. A model can produce an answer that sounds complete even when the process behind it was wrong.

The fix doesn't need to be complicated:

  • keep the source files
  • record the key decisions
  • show what changed
  • record failures instead of hiding them
  • mark outputs that still need approval
  • keep a clear record of whether something was published, sent, rejected or left for review

The goal is simple: someone should be able to look at the workflow and understand what happened.

Keep judgment in the loop

Not every decision should be automated.

Questions about rights, factual claims, payments, access, publishing, or anything that affects other people often need a person to make the final call.

That doesn't mean keeping the whole process manual. Automate the research, the preparation, the sorting, the drafting and the checks. Then give the person what they need to decide.

The system should reduce the work it takes to make a decision. It shouldn't hide the fact that a decision was made.

What that looks like in things I've built

  • Bloodhound, my research agent, stores every accepted fact with the source it came from and keeps a manifest of the pages it read. A lead only counts as qualified with public evidence behind it.
  • SoftDoctor Studio ties each approval to the exact script and video file that was approved. Change the file and the approval no longer applies. Publishing is switched off until the owner authorises it separately.
  • The WhatsApp document bridge sends the finished file back into the same chat the original came from, so the person who asked can see the result straight away.

Good automation gives you speed without taking away your ability to see what happened.

That is the standard I build to: automate the repetitive work, keep the important decisions visible, and make every meaningful step easy to check.

Got a task you do every week? Send it to me.

Describe it in a couple of sentences. I'll tell you honestly whether it's worth automating and what I'd build. You don't pay anything unless it saves you time.

Replies in English or Romanian.