NetAuto Academy

Start Here

Manual vs Automated Workflows

Beginner10 min read

What you'll learn

  • What actually changes — and what doesn't — when a manual task becomes automated
  • How to compare a manual and automated version of the same workflow, step by step
  • Why the devices, connection method, and commands stay identical either way
  • Where a human still needs to review the result, even after automating
  • How to walk through a second, different workflow (config backup) using the same lens
🎓 Teach This Lesson

Listen to a guided explanation of this lesson.

Spoken narration isn't supported in this browser.

The same task, two different ways of doing it

The previous lesson made the case for why engineers automate. This one gets concrete: what does "manual" actually look like next to "automated," step by step, for a real task?

Take configuration backup — pulling show running-config from every switch and saving it somewhere safe, so there's a known-good copy to fall back to if a change goes wrong.

Manual, that's: SSH into switch one, run show running-config, copy the output, save it to a file named for that switch, log out. SSH into switch two. Same command. Same copy-paste. Same save. Log out. Repeat for every switch on the list.

Automated, the task doesn't change — you still connect to each switch and pull the same command — but a script does the connecting, the running, and the saving, for every device on the list, and hands you a short report at the end: how many succeeded, and which ones (if any) didn't.

Side by side

Manual
  1. Engineer
  2. SSH to switch
  3. Switch 1run 'show running-config', save output
  4. Repeat
  5. Switch 2run 'show running-config', save output
  6. Repeat
  7. Switch 3run 'show running-config', save output
Automated
  1. Engineer
  2. Automation script
  3. Multiple devicessame command, same save, every device
  4. Collect results
  5. Validatedid every device actually respond?
  6. Reporte.g. '58 saved, 2 unreachable: SW-11, SW-40'
Quick checkConcept check
In the comparison above, what stays exactly the same between the manual and automated versions of the backup task?

What's genuinely different

Look closely at the automated column and you'll notice it has three steps the manual one doesn't: Collect results, Validate, and Report. That's not decoration — it's the part that makes automation trustworthy instead of just fast.

When you do this manually, "did it work?" gets answered in your head, switch by switch, as you go. When a script does it, that check has to happen explicitly, in code, because nothing else is watching. That's why an automated workflow always ends with a validation step and a summary — not because automation is more cautious than a person, but because it has to replace the judgment a person was applying live.

Where the human still fits in

Automating the backup doesn't remove the engineer from the loop — it moves them from doing all sixty backups manually to reading a one-line report and deciding what to do about the two switches that didn't respond. That's still a human decision. It's just a much smaller, more focused one.

A second example: compliance checking

The same comparison holds for a completely different task. Say the goal is confirming every switch in a wiring closet still has the correct VLAN trunk configuration after a vendor firmware upgrade.

Manually: SSH into each switch, run show interfaces trunk, read the allowed-VLAN list, compare it against what it's supposed to be, note any mismatch, log out, move to the next switch.

Automated: a script connects to every switch on the list, runs the same show interfaces trunk, compares the output against the expected VLAN list, and reports only the switches that don't match — instead of a full transcript of fifty switches that were all fine.

That last part is worth noticing: a good automated report doesn't just dump more data on you. It surfaces what actually needs attention and quietly confirms the rest.

Quick checkScenario
A script automates the VLAN trunk compliance check above. What's the best description of what changes for the engineer?
Quick checkWorkflow check
Put these stages of the automated backup workflow in the correct order.

Why the report still needs a person

It's tempting to think "automated" means "no oversight needed." It doesn't. A script can succeed or fail in ways that genuinely need a person's judgment: a switch that's unreachable because of a real outage, output that doesn't match the expected format because someone changed the config by hand outside the script, or a result that's technically "correct" but still worth a second look.

Automation reports; people decide

An automated workflow's job is to do the repeating and surface what's worth looking at. Deciding what to do about switch 11 being unreachable — is it down, misconfigured, or just slow to respond? — is still the engineer's call. Automation narrows down what needs attention; it doesn't remove the need for attention.

Quick checkMyth check
Which statement about automating a workflow like config backup or compliance checking is accurate?

Key takeaways

  • A manual and an automated version of the same task hit the same devices, over the same connection, running the same commands — only who repeats the steps changes.
  • An automated workflow adds explicit collect / validate / report steps because nothing else is watching the way a person watches while doing it manually.
  • A good automated report surfaces what needs attention (mismatches, failures) rather than dumping every output on the engineer.
  • Automation doesn't remove human judgment from the loop — it moves that judgment from 'doing every step' to 'deciding what to do about the exceptions.'
  • The same manual-vs-automated comparison applies to any repetitive, well-defined, multi-device task — backup and compliance checking are just two examples.

Done with this lesson?

Next lesson

What Can Network Automation Automate?