For when
“We bought AI tools, but useful adoption is patchy.”
Usually commissioned by: IT leader, operations leader, L&D sponsor.
What you get
- Three to five agreed workflows configured in your existing tools
- Working practice for each: inputs, prompts or templates, review step, and where the output goes
- Safe-use guidance tied to your information classes, not a generic policy
- Baseline and follow-up measurement of effort, quality and adoption
- Hand-over pack so the team can add new workflows without us
Acceptance condition
Staff can run the agreed workflows with the required review step, and the follow-up measurement has been shared with the sponsor.
How it runs
- 1
Select workflows with the team lead using the opportunity scorecard
- 2
Measure the current effort and quality on real work
- 3
Configure and rehearse each workflow with the people who do the work
- 4
Run it for two to four weeks, then measure again and adjust
It may conclude…
Some workflows are better left manual or handled by ordinary automation. We drop them rather than force them.
Not included
- New tool procurement
- Custom software development
- Generic AI awareness training
Read before you decide
Free guides that cover the same ground. Plenty of teams get what they need from these alone.
How to improve Copilot or ChatGPT adoption across a team
Licences are not adoption. How to turn Copilot, ChatGPT or Claude seats into agreed working practices for three workflows, with safe-use rules and measures.
How to measure AI adoption — and when to retire an AI workflow
A workflow health review for AI in production: usage, quality, review effort, incidents, cost and maintenance, plus clear criteria to keep, extend or retire.
Faster research briefs and proposals from approved information
How to draft research briefs and proposals faster from an approved content library, with citations, expert review, and the bid/no-bid decision kept human.
Can staff use AI with internal documents?
How to decide whether staff may use AI with internal documents: approve a workflow's data flow, match information classes to tool tiers, and check the contract.
Discuss a Team Workflow Activation
Send a short project brief. A person reads it and replies with whether this engagement fits, a different one would, or none is needed.