There’s a tempting failure mode in software: the more sophisticated the automation, the more dashboards, configuration screens, and “control surfaces” the team builds around it. The system is doing more work, but the user is doing more work too — just a different kind.
The best automation we’ve built has the opposite shape. It’s a thing the team used to do, that quietly stops appearing on anyone’s calendar. No new tab to check, no new tool to learn, no new “ops” role to staff. Just an absence.
That absence is the product. Everything else — the model, the orchestration, the infrastructure — is plumbing. The only thing the team should notice is that the work that drained them isn’t draining them anymore.
This is the bar we hold ourselves to: did the team get an hour back, or did they just get a new screen?
— Roger