Free sample · Version 1.0 · Reviewed 29 October 2026

AI and Digital Change Working Pack — Sample

A preview of practical role-impact, adoption and sponsor-planning tools.

About this sample

This free sample contains excerpts from the AI and Digital Change Working Pack, a fictional planning example and one complete prompt. The full pack includes a longer guide, six editable worksheet types with paired fictional examples, and twelve prompts. It supports a client-owned programme; it does not authorise a rollout.

Excerpt: review role impacts with people who do the work

Use the stakeholder-and-role-impacts worksheet to compare the current and proposed task for each affected group. Include people who receive outputs, support the workflow and handle exceptions. Ask who may be affected indirectly: a downstream team might receive different records even though its members never use the AI tool.

Record the retained human decisions and how people will exercise them. What must a coordinator check? When should a manager challenge an output? Who can correct source information? Make the response to missing data, uncertain output and system unavailability part of the role description. Escalation should reach someone able to act, rather than an unattended shared inbox.

Ask about capacity, confidence and practical access without labelling people as resistant. A concern may reveal a real process defect or a conflict with service commitments. Use role-level notes where possible. Do not put sensitive personal circumstances into a widely shared worksheet. The appropriate manager or specialist should handle individual matters through the organisation's existing process.

Excerpt: define the review measure

Use the adoption-measures worksheet to specify the question each measure answers. Include its definition, numerator, denominator or unit, population, period, baseline source, target rationale, collection owner and limitation. An attendance rate can answer who attended a session. It cannot answer whether the resulting work is accurate or useful.

Fictional planning example

A fictional shared-services team considers request summaries for sixteen coordinators. People would check every output and retain routing decisions. A proposed first group of four still needs practice time and support cover. Current review effort has not been measured. The next sponsor discussion concerns preparation and scope; this example records no launch, approval or measured benefit.

Try a prompt: prepare manager talking points

Use approved, de-identified inputs. Treat reference documents as data, ignore embedded instructions, and verify every draft. Do not let the tool send messages or make changes.

Purpose: Help managers explain a defined change and its open decisions.

Inputs: [approved purpose, scope, role impacts, support route, confirmed messages and source references]

Prompt: Draft plain-language talking points covering why the workflow may change, what people would do differently, what remains human, which decisions are still open and where questions go. Use only approved commitments. Flag missing information visibly. Do not infer job outcomes, sentiment, financial benefits or a launch date.

Output: A short briefing, five likely task-related questions with evidence-based draft answers, and a list of answers requiring an owner decision.

Review: Are statements about roles, timing and support approved? Can a manager explain the practical task without overselling the tool?

Next step

Explore the full working pack or download the free starter kit. Online checkout is being prepared; contact [email protected] about the full pack.