Sometimes the smartest automation is no automation at all.

Eliminate before you accelerate.

Question whether the task contributes to an outcome you still care about. A report nobody reads may need to stop, not become easier to generate. Confirm the consequence of removing a task with its owner before changing it.

Simplify before you connect.

A standard intake form, a shared checklist, or one clear decision-maker can make the process easier to follow. Try that smaller change before connecting several systems. Keep a record of the result.

Assist before you delegate.

For judgment-heavy work, begin with a draft or recommendation. Preserve approval over commitments, sensitive information, and external communication. The boundaries should be visible to the person using the workflow.

Automate only what you can inspect.

Specify the trigger, expected input, intended action, checks, failure alert, and recovery procedure. Test with safe sample data. Give a person ownership of the result and a way to disable the workflow.

Choose a reversible experiment.

Start with a low-risk task and a manual fallback. Compare total effort before and after, including review and maintenance. Keep the change because it works for your circumstances, not because automation itself became the goal.