Uptake below expectations
Distinguishes reported adoption from everyday use and identifies where people struggle to make the change stick. Findings explain the barriers behind stalled uptake, supported by anonymous evidence.
— Operations & Process
Identifies where adoption of a new system, process or way of working stalls after go-live, with an evidence-backed report on barriers, workarounds and differences between functions.
1–2 weeks → ~15 minutes
For one complete, review-ready pass
No coding required
— USE CASES
Distinguishes reported adoption from everyday use and identifies where people struggle to make the change stick. Findings explain the barriers behind stalled uptake, supported by anonymous evidence.
Surfaces the informal practices people use instead of the intended system or process. The report explains what drives these workarounds, helping leaders understand whether the friction lies in the change itself or the support around it.
Highlights differences in use and barriers across functions. This gives advisory teams a grounded basis for tailoring support rather than treating adoption as a single organisation-wide issue.
Provides a reviewed diagnostic of how a new way of working operates in practice. Non-attributed quotations and concrete examples make the findings useful for leadership discussions about where attention is needed.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
The run pauses for a person to confirm the process steps that matter before the deliverable is composed.
Findings on the end-to-end process are written up as a document that reads like professional output, with each claim tied back to a process step.
Each process step is assessed against explicit criteria you control, so the same standard is applied across the end-to-end process on every run.
The run works from process documentation and run data you supply, so conclusions about the end-to-end process are anchored to your evidence rather than general model knowledge.
Going live does not mean a new system or process becomes part of everyday work. Uptake below expectations is the typical trigger — distinguishes reported adoption from everyday use and identifies where people struggle to make the change stick. Findings explain the barriers behind stalled uptake, supported by anonymous evidence. Get it right and the conclusion holds up in the room; get it rushed and it gets picked apart. Either way it costs roughly 1–2 weeks of experienced attention.
Skillsize turns that work into a Skill: you supply the material, and what comes back is a reviewed post-go-live adoption report, with findings on where adoption stalls and the reasons behind each stall. The criteria, ordering and review points that make the answer trustworthy are encoded in the Skill itself — which is the difference between a structured method and a prompt someone pastes in. The practical effect: 1–2 weeks of manual work becomes a ~15 minutes run, held to an identical standard on the tenth engagement as on the first.
Post Go-Live Adoption exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Operating Model Mapper
Maps how an organisation actually operates using anonymous accounts from its people, producing an evidence-backed diagnostic of responsibilities, decisions, handoffs and duplicated effort.
AI Readiness Assessment
Assesses AI readiness through anonymous staff evidence, identifying where AI can improve day-to-day work and the practical barriers that could prevent those gains.
Project status digest
Reads a set of weekly status notes for progress, blockers and RAG, charts the trend, and writes an executive digest focused on trajectory.