Human-in-the-Loop Automation Design
Why Humans Still Matter¶
Automation improves speed and consistency, but not all decisions are deterministic.
Human judgment remains essential when:
- Business impact is high
- Data confidence is low
- Multiple valid remediation options exist
- Context exists outside machine-readable systems
The goal is not manual work everywhere. The goal is human authority at the right decision points.
Where To Place Approval Gates¶
Typical gate locations:
- After plan generation, before write execution
- Before scope expansion beyond canary or first batch
- Before rollback in ambiguous failure states
- Before applying changes flagged as high risk
Approval should be role-based and traceable.
Effective Dry-Run Reviews¶
A useful dry-run should include:
- Proposed change diff per device
- Risk classification per target
- Confidence indicators and parser quality
- Expected service impact statements
If dry-run output is unclear, operators will either reject safe changes or approve risky ones blindly.
Intervention Design¶
Human intervention should be explicit:
- Pause points with timeout policy
- "Approve", "reject", and "defer" outcomes
- Escalation target when no decision is made
- Safe default behaviour on timeout (usually abort)
Production Checklist¶
- Human approval gates are defined for high-risk operations
- Dry-run artifacts are easy to review and compare
- Approval decisions are logged with identity and timestamp
- Timeout behaviour is deterministic and safe
- Operators can pause or stop execution at controlled points
Anti-Patterns¶
- Human approval as a rubber-stamp with poor context
- Approval required for every trivial operation
- No owner assigned to pending approval actions
- Auto-approve behaviour on gate timeout
Key Takeaway¶
Human-in-the-loop design is about targeted control, not friction. Place humans where ambiguity and impact are highest.
Between the Lines
Kipling's If— asks you to trust yourself when everyone doubts you, and to make allowance for their doubting all the same. That is a good approval gate in a sentence: enough confidence to proceed, enough humility to want a second pair of eyes on the days it matters.
The poem is about becoming a person, not designing a process. The overlap is not an accident — both are asking where your judgement belongs, and where it is better shared.
Continue the Series¶
- Series Index: Production-Grade Network Automation Principles
- Previous: Part 12 - Secrets and Credentials in Enterprise Automation
- Next: Part 14 - Knowing When Not to Automate
Need help applying this in a live Cisco environment?
This guide is part of the Nautomation Prime Foundation and stays free to read, share, and reuse. If you want the pattern implemented, governed, or adapted for your estate, that is paid engineering work — start a discovery conversation or review how Nautomation Prime delivers engagements. If you are a registered UK charity or CIC, there is a free and low-cost route instead.