Duration: 1 Day
Skills Gained
By the end of this course, participants will be able to:
-
Tell a personal time-saver from a workflow the team should fund
-
Choose two workflows using value, how often they happen, and how easy they are to undo
-
Name the owner, the reviewer, and the person who handles the exception
-
Write the condition that ends a pilot, before the pilot starts
-
Brief the team and the sponsor on the same 90-day plan
Who Can Benefit
This course is designed for:
-
People managers, team leads, and directors who sponsor how the team uses AI
-
Operations and product owners accountable for the quality of the work
-
Chiefs of staff and program leads who shape how a team adopts a tool
Prerequisites
Participants should enter this course with:
Organizational Objectives
This course assists organizations to:
-
Move from scattered chat use to two workflows with an owner
-
Make the review and the exception path visible before anyone scales a tool
-
Give sponsors a 90-day plan they can continue or stop
-
Keep judgment with the manager, including where a tool takes steps on its own
Software
A modern web browser and an internet connection. No administrator access. The exercises are plans, briefs, and a pilot card. A chat tool is available in the lab for illustrating a workflow, and is not required to finish.
Module 1 — Choose the Two Workflows
By the end of this module, you will be able to separate a personal shortcut from work the team should manage.
-
A faster afternoon for one person is not the same as a better decision for the team
-
Fits: drafts, summaries, sorting, a first pass at an analysis, notes into actions
-
Stays with a person: a regulated decision, a new judgment, a promise to a customer
-
A license for everyone still needs an owner and a check
Hands-on Lab: Score three workflows from your team, or from the packet. Keep two. Write why you set the third aside.
Module 2 — Name the Owner
By the end of this module, you will be able to describe one workflow on a single page a sponsor can approve.
-
What starts it, what goes in, what the tool does, who checks it, and who uses the result
-
When a chat habit is enough, and when the team needs something configured
-
Who drafts, who reviews, and who owns the exception
-
What data may be used, stated before the pilot
Hands-on Lab: Write a one-page brief for one workflow. A partner should be able to say who is accountable without a meeting.
Module 3 — Decide What Ends the Pilot
By the end of this module, you will be able to say what good enough means, and what ends the trial.
-
The check a reviewer actually does. A number that does not trace to a source does not send
-
What the pilot costs: seats, review time, and rework
-
How this fails quietly: side use, a paste into the system of record, a prompt that becomes folklore
-
A stop line in one sentence. If review time is not down at day 30, the pilot ends
Hands-on Lab: Draft a pilot card: the bet, the measure, the check, the stop line, and the review date.
Module 4 — Brief the Team and the Sponsor
By the end of this module, you will be able to tell both rooms the same plan.
-
What the team may do, what they say they did, and what stays out
-
The manager reviews. Judgment stays with the manager
-
Ninety days: one workflow and a measure, then a second workflow or a stop
-
The sponsor page and the team page say the same thing
Hands-on Lab: Write the 90-day plan and a short sponsor note. A partner checks them against the pilot card.
