Workshop
The Team Writes the Plan: an AI and automation workshop for department teams
A working session where the people who do the work decide what to automate first.
Leadership has asked every part of the business to adopt AI. Most teams will wait to be told what changes. Yours can hand leadership a ranked plan before anyone writes one on its behalf.
What this is
One facilitated working session with your team. The people who do the work map it, examine it and produce a ranked list of what to automate first. They own the recommendation. Jack runs the room, keeps it honest and writes it up.
Who it is for
Finance, operations, revenue cycle, compliance and human resources teams, in professional services firms and health systems. Any department whose leader has been asked what AI will change and would rather answer with the team's own plan than wait for one.
How the session runs
1.Map the real work
The real week, the real processes. Each person lays out what they spend time on, not the job description. The team sees, often for the first time, where the effort sits.
2.Try on the future role
Before anyone is asked what to automate, the team walks through what the job looks like once routine work is handled elsewhere. People volunteer far more when they can see where they land.
3.Work a live example
Using one real use case you supply in advance, the team applies automation to something they already recognize. No hypotheticals.
4.Assess, role by role
What could be automated, what should not be, and what would break if it were. The team makes those calls. Jack has sat through enough of these sessions to know the quiet person at the end of the table usually has the list already.
5.Rank it
Every candidate is scored on business impact, ease of implementation and risk. The result is a priority order the team can defend.
6.Write it up
Jack produces the report. It goes to leadership under the team's name, with an owner and a first action attached to every item.
What you get
- A clear picture of how the department's work is distributed today.
- A force-ranked automation priority list, built and defended by the team.
- A written recommendation ready for leadership.
- A team that authored the change rather than absorbed it.
What Jack needs from you
- Time: two half-day sessions, live or virtual.
- People: the whole team, one room, for the duration.
- In advance: one real use case to work from.
- From leadership: nothing. The department initiates this.
What it will not do
It will not pick the software. It will not replace a controls review before anything goes live. And a team that has already been told the answer will not produce an honest list, so the session is not run after the decision has been made.
How you will know it worked
Leadership receives a ranked automation plan from the department before one is written for it. Every person on the team can name what changes in their own role. The first item is in build within a quarter.
Afterwards
For the top-ranked items, Jack works with the team to design and stand up the automation, so the list turns into working process rather than a document that ages on a shared drive.
Questions department leaders ask
How long does it take?
Two half-day sessions. Live in one room, or virtual.
Who should be in the room?
The whole team, including the people who do the routine work. The session fails if only managers attend.
Do we need leadership approval?
No. The department initiates it and leadership receives the plan.
What do we send in advance?
One real use case the team already recognizes. Jack reviews it before the first session.
What happens afterward?
The team receives the written report under its name. For the top-ranked items, Jack can work with the team to build the automation.
Is this a keynote?
No. It is a working session. Jack speaks as little as the room allows.
The next step
A 30-minute discovery call about your team, the use case and the date. A proposal follows within 48 hours.