IT & Data
Release note and change communication drafting
Turn technical change records and commit history into plain-English release notes and user communications, differentiated by audience — store colleagues, head office users, and IT support.
50–70%
reduction in change communication drafting time
Opportunity assessment
Negligible commercial impact. Saves time at the margins but won't move the needle on revenue or profit.
Very easy to implement. Ready-to-use tools exist. Can be up and running in days or weeks with minimal technical resource.
Light data requirements. Uses straightforward inputs — documents, product descriptions, customer records — that are usually accessible with minimal prep.
Very low risk. Fully internal use. A person checks everything before it goes further. Worst case is a minor internal inconvenience.
Very easy to absorb. Runs quietly in the background or gives people a helpful new input. Makes everyday work easier with almost no friction.
Tooling required
Things to consider
Poor change communication drives avoidable service desk volume every release. The saving shows up in ticket counts the week after a release, not in the drafting time.
Audience differentiation is where the model adds real value. The same change needs three lengths and three vocabularies, and nobody has time to write three versions by hand.
Anything describing a change to a regulated or safety-related process still needs review by the process owner before it goes out.
Experiment starter: Draft store-facing notes for the next three releases and compare service desk volume in the following week against the previous three releases of similar size.
Go deeper in the playbook
Section — Opportunity Identification, including the AI Opportunity Assessment ScorecardSection — The Experimentation FrameworkThis is an augmentation opportunity — see the relevant playbook section for how to approach it.More in IT & Data
IT service desk triage and deflection
Classify and route inbound IT tickets, resolve common requests through self-service, and draft first-line responses for the remainder using the internal knowledge base and past resolutions.
AI coding assistance for internal development
Equip internal developers with an AI coding assistant for code generation, refactoring, test writing, and code review, integrated into the existing development environment and review process.
Legacy system documentation generation
Generate readable documentation for undocumented legacy systems — data models, integration points, business logic, and dependencies — from source code, database schemas, and configuration.
AI Transformation Playbook
Ready to assess your own opportunities?
The playbook gives you the full 150-opportunity directory, scoring tools, and 100+ templates for every stage of an AI transformation programme.