Browse the book & resources

Chapter 04 / 20

4. Where AI Fits—and Where It Does Not

Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.

A ten-minute task does not necessarily improve when an assistant joins it. The instruction takes time; verification takes time; sometimes direct work is simpler. On another task, an agent may read dozens of files, draft a migration, and leave a human with a valuable starting point. The decision depends less on the name of the tool than on the shape and risk of the work.

Ask five questions before granting it a role. Is the result checkable? A generated test can be run, but a convincing explanation of a poorly understood failure may be harder to validate. Is the context available and permitted? An agent cannot infer undocumented customer constraints, and access to private data is not a free convenience. Is the action reversible? Drafting a note is different from changing production data. Who will own the outcome? A reviewer needs enough time and expertise to disagree. What is the credible alternative? Better documentation, a smaller change, a fixed CI pipeline, or a direct human conversation may solve the problem at lower cost.

This yields four legitimate decisions. Use AI for bounded, testable work with a named owner and an inexpensive verification path. Improve the workflow first if waiting, poor context, or oversized changes are the real constraint. Defer when measurement or permissions are not ready. Decline when disclosure, safety, weak verification, or deliberate skill practice makes use inappropriate. None is a moral verdict about an engineer.

The desk-researched account of non-use collects reasons employees give for declining AI: high-context decisions, short tasks, and independent practice. It does not establish a formal safe-to-decline policy or prove that performance reviews reward those choices. Leaders need to make the policy real by rewarding good judgment, including a carefully reasoned "no," not tracking prompts as a proxy for effort.

Autonomy should rise only as evaluation and reversibility improve. A suggestion in a local editor, a bot opening a PR, and an agent with production write access are three different commitments. Require clear permissions, traces of actions, and human approval before consequential or irreversible changes. A human-in-the-loop label alone is not a safeguard if the human is handed more material than they can meaningfully review.

At the junction: Choose one recurring task and fill in: what could AI do, what could a non-AI change do, how would each be verified, and who would absorb any error? If none of the outcomes can be checked within a reasonable window, do not scale the experiment yet.

No external sources cited in this chapter. Browse all references →