AI Automation Planning: Define the Task Before the Tool

Describe la tarea con precisión.

Comience con una actividad repetible. Registre sus entradas, salidas esperadas, excepciones y el responsable del resultado. Si la tarea no se puede describir claramente, dedique tiempo a comprenderla antes de elegir un método de automatización. Algunos requisitos pueden ajustarse mejor a reglas sencillas que un enfoque basado en IA.

Defina cómo se ve un resultado útil.

Cree ejemplos representativos que el equipo pueda revisar. Incluya casos incómodos, entradas incompletas y situaciones que deberían derivarse a una persona. Acuerde cómo se evaluarán los resultados antes de ampliar el flujo de trabajo. La evaluación debe reflejar la tarea real, en lugar de una demostración impresionante pero no relacionada.

Mantener la revisión y el acceso explícitos.

Decida qué salidas requieren aprobación humana y a qué información puede acceder el flujo de trabajo. Analice el manejo de fallas y la ruta para corregir una salida. Evite otorgar un acceso más amplio simplemente porque sea conveniente durante un prototipo. La propiedad de la decisión final debe permanecer visible.

Revise el piloto antes de expandirlo.

Compare el piloto con el flujo de trabajo actual según los criterios que acordó. Limitaciones de registro y preguntas pendientes. Una implementación más amplia es una decisión separada, informada por los resultados del piloto, los requisitos operativos y las personas que lo respaldarán.

Scope the pilot before selecting a tool

Choose one task with a clear start and finish. Observe how a person handles it today, including the checks they perform before acting. Identify whether the proposed automation prepares information, recommends a decision or performs an action; these require different review boundaries.

Build a small, representative evaluation set with agreed expected outcomes. Test incomplete inputs, ambiguous requests and cases outside the intended scope. Record incorrect outputs and the work needed to correct them. Compare the pilot with the existing process using the same task definition, then decide whether to revise, expand or stop. Keep any production rollout separate from the initial experiment.

A one-page automation opportunity sheet

Complete this sheet with the person doing the task and the person who would operate the automation. It should expose uncertainty before a technical demonstration.

• Task boundary: trigger, required inputs, intended output and actions the automation must never take.
• Current process: responsible role, checks, common exceptions and existing escalation routes.
• Candidate method: simple rules, assisted drafting or another approach, with the reason for considering it.
• Evaluation: representative cases, unacceptable errors and the person reviewing each result.
• Operating plan: access, monitoring, fallback, correction ownership and expected running costs.
• Decision gate: evidence needed to continue, revise the scope or end the pilot.

Avoid automating an unclear decision

If staff disagree about the correct outcome, resolve the rule or policy before asking a tool to reproduce it. A model cannot settle an unowned business decision merely by generating a confident answer.

Do not assess only successful outputs. Review incorrect actions, uncertain cases and time spent checking results. Keep access restricted to the information needed for the pilot, and avoid presenting a prototype demonstration as evidence that the wider workflow is ready to operate without supervision.

Does automation always need AI?

No. A stable task with explicit conditions may be better served by rules or an ordinary software workflow. Consider AI where the task warrants evaluation, and compare it against a simpler baseline rather than assuming the more complex option is preferable.

ILLUSTRATIVE PLANNING EXAMPLE

Example: routing incoming support requests

A support team wants to route enquiries by subject. Define the available categories and give the pilot a representative set of anonymized messages. Include messages covering two topics and requests that do not fit any category. Decide which uncertain results return to a person rather than moving straight into a queue.

Record the routing decision, reviewer correction and reason for escalation. Use that evidence to decide whether to adjust the task, change the method or stop the pilot.

FURTHER READING

Official resources to explore

Explore the related official guidance below. The templates and examples are practical starting points to adapt to your own project.

• NIST AI Risk Management Framework Playbook