HomeGuidesChoose your first AI coworker workflow
Workflow selection

Start where useful work is easy to recognize.

Choose a first workflow by weighing repetition, available evidence, review effort, and the consequence of an error.

A practical playbook with an illustrative example.

# your-team
JaredILLUSTRATIVE WORKFLOW
Compare these workflows by trigger, sources, private deliverable, reviewer, and consequence of error. Flag missing prerequisites. Recommend the smallest useful pilot and explain why it is easier to evaluate. Do not contact anyone or change existing workflows.
A specific outcome + a clear boundary
Interactive example. No real customer data or external actions.
Start with the outcome

Make the work easier to move forward.

A strong first workflow gathers known information, prepares something a teammate needs, and returns it to an accountable reviewer. The team can recognize a good result because it has done the work before. Choose a narrow handoff that improves an existing habit.

The most frustrating job may have unclear ownership, missing inputs, or cases that each demand new judgment. Adding an AI coworker does not resolve those underlying decisions. Choose a workflow whose boundaries you can explain.

What to bring to the task

  • Three to five recurring tasks that consume real team attention
  • A recent example and source set for each candidate
  • The person who owns the result and can judge it
  • The consequence if the output is incomplete or wrong
A practical working method

From context to a useful result.

  1. List handoffs rather than broad roles

    Replace 'help sales' with 'prepare a follow-up draft after a proposal has gone unanswered.' Replace 'manage projects' with 'assemble open decisions before the weekly review.' Each candidate should have a clear beginning, a useful deliverable, and a point where another person takes responsibility.

  2. Apply three readiness gates

    Check that the necessary information exists, a reviewer can access and understand it, and errors can be caught before causing harm. If any gate fails, fix the underlying gap or choose another candidate. A high-value idea with no reliable source is a preparation project, not a ready pilot.

  3. Compare the remaining candidates

    For each, mark repetition, input clarity, review ease, and consequence as favorable, mixed, or difficult. Add a sentence of evidence beside every judgment. Prefer frequent work with recognizable outputs and inexpensive correction. Avoid a precise-looking score that hides one unacceptable risk inside several attractive benefits.

  4. Choose the smallest useful slice

    Reduce the winning candidate to one audience, project, or reporting period. A first briefing might cover launch decisions only; a client report might cover one active engagement. Keep preparation private during the trial. Verify that this smaller output still helps someone make a real decision or finish existing work.

  5. Name the reason to continue

    Write acceptance criteria and a review date. Ask what would convince the owner to keep using the result, and what failure would require a pause. Save the manual example for comparison. If nobody can describe a useful result, refine the candidate before starting.

The human review checkpoint

Workflow selection is a planning decision. It does not grant access to every possible source or permission to send messages, publish content, or change records. Those steps need an explicit scope and the appropriate authorization when they become relevant.

Before you make it a routine

  • The task already matters to a specific person
  • Its information and ownership are available
  • A reviewer can recognize and correct errors
  • The pilot is narrow but produces a genuinely useful result

A few useful questions

Should I choose the task that takes the most time?

Consider time alongside readiness and consequence. A shorter, repetitive preparation task can be a better first experiment if the result is easier to verify and learn from.

What if every candidate has messy inputs?

Choose one and define the minimum source record it needs. Clarify owners, status meanings, and dates first. Then test preparation from that bounded record before widening the source set.

Keep exploring

Related playbooks