Boundary cards for augment vs automate
Use a compact reference to choose automate, augment, or human-owned boundaries for common task patterns.
A team is deciding where AI should own, assist, or stay behind a human decision. Use task properties to set the AI boundary, then test it in workflow. battlecard When someone says automate it This task is repetitive, so AI should own it. A teammate is pushing for automation based only on repetition. Your line Repetition is one signal. Before we automate, let's check input stability, reversibility, consequence, and exception rate. Treating repetitive as automatically safe. It accepts the useful signal while adding the missing task-boundary tests. comparison Fast distinction Automate vs augment The boundary is ownership, not whether AI…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in