How to run an AI workflow training pilot for a design team
Published
An AI workflow training pilot should teach a design team to complete a real task with approved inputs and a clear review process. Measure the whole task, including preparation and rework, before expanding the workflow. A successful demonstration is a starting point; independent repeat use is the test.
The pilot below is a suggested operating plan, not a guaranteed delivery schedule or a report of measured client results. Its scope can stay small while still answering whether the training changed how the team works.
Which workflow belongs in the first pilot?
Choose a recurring task with an observable output and a person qualified to review it. Suitable candidates might include preparing a draft research discussion guide from an approved brief or checking interface copy against an established terminology list.
Document the task before adding AI. Identify its trigger, inputs, output, recipient, and usual failure points. Avoid a task whose quality nobody can judge or whose necessary data the team cannot use in an approved environment.
Peter Yang’s guest article in Lenny’s Newsletter on company AI adoption emphasizes practical instruction and focused use cases rather than a broad request to use AI more. It also discusses internal enthusiasts helping colleagues learn. A bounded pilot gives that teaching a concrete task.
What must be approved before training starts?
Name a workflow owner and a reviewer. Confirm which tools, accounts, and data categories the organization permits. Approval to use a tool does not automatically authorize uploading client research, personal information, or confidential design files.
Write a short input rule that participants can follow without interpreting policy during a workshop. When permission is unresolved, use explicitly synthetic examples or materials cleared for the exercise. Label synthetic research as practice material; it must never become evidence about actual customers.
- Record where approved source files live and who may access them.
- Identify what must be removed or withheld before a task starts.
- Specify where generated drafts and review notes may be stored.
- Name the person who handles a suspected data exposure or other policy breach.
Keep access decisions with the responsible internal owners. A trainer should not quietly expand permissions to make a demonstration work.
How should the team establish a baseline?
Observe the current method on representative tasks before the workshop. Record preparation time, working time, review time, corrections, and whether the result met its acceptance criteria. Note task difficulty so a simple example does not become the comparison for a harder assignment.
Define quality checks before seeing the AI output. For a hypothetical discussion-guide workflow, the reviewer might check that questions address the approved research goals, avoid leading participants, and do not introduce unsupported customer claims. Those criteria are illustrative and need adaptation to the actual research plan.
Measure the assisted method using the same categories. Count discarded attempts and repairs. A fast first draft can still create more work for the reviewer, so generation time alone is an incomplete measure.
What should the workshop and practice include?
Demonstrate the full task using the approved materials. Explain what context the prompt supplies, how to inspect the output, and when to stop. Show a flawed result and the review that catches it; a polished example alone does not teach judgment.
Then ask participants to perform a different example themselves. The trainer should observe where they hesitate rather than completing the task for them. Record recurring questions in the workflow instructions.
A suggested sequence is a preparation session, a workshop, supervised practice, and an independent check. Set the duration around task frequency and participant availability. If the workflow runs monthly, a short training event cannot prove sustained monthly adoption.
During practice, preserve a manual route for tasks the workflow cannot handle. Record why a participant chose that route. It may reveal missing context, unsuitable inputs, or a task that should remain manual.
What should an independent practice assignment look like?
Illustrative exercise, not a measured client result: a designer uses an approved terminology list to review interface copy. The practice file includes an outdated product name, an ambiguous error message, and a sentence that already follows the rules. The reviewer knows which findings are warranted before the exercise starts.
- Input: provide the approved copy file and terminology list. Include no customer records.
- Output: request the original phrase, proposed change, and the specific rule supporting each suggestion.
- Quality check: reject invented terminology and edits that change the product’s meaning. Confirm the already-correct sentence remains intact.
- Effort record: include preparation, generation, review, corrections, and any discarded attempt.
- Independent check: repeat with another copy file while the trainer observes silently. Revise the instructions where participants need intervention before expanding the workflow.
What should remain after the trainer leaves?
Deliver a runnable instruction sheet with the task trigger, approved inputs, prompt, expected output, review checklist, and escalation contact. Include an acceptable example and a flawed example with the reason it fails. Record the tool and configuration used so later changes can be investigated.
The owner should also receive the practice findings and a list of unresolved limits. Ask a participant who did not write the instructions to execute the task from them. Missing steps become visible quickly when the author stays quiet.
When should the team expand, revise, or stop?
Agree on decision criteria before the pilot ends. Expand when participants can repeat the task with acceptable quality, permissions remain appropriate, and the complete effort justifies continued use. Revise when the task is promising but review or instructions need repair. Stop when risk or rework outweighs the benefit.
Teams comparing delivery partners can use the AI workflow agency comparison. A focused AI workflow training engagement should leave the internal owner able to run that decision process again.
