Establishing the current operating model
Provides a grounded account of how the organisation works today, supported by quoted evidence from people across teams. Gives advisory teams a shared baseline for operating model discussions.
— Operations & Process
Maps how an organisation actually operates using anonymous accounts from its people, producing an evidence-backed diagnostic of responsibilities, decisions, handoffs and duplicated effort.
1–2 weeks → ~15 minutes
For one complete, review-ready pass
No coding required
— USE CASES
Provides a grounded account of how the organisation works today, supported by quoted evidence from people across teams. Gives advisory teams a shared baseline for operating model discussions.
Highlights where teams describe different decision rights, working practices or responsibilities. Makes local variations visible rather than presenting a single account that conceals disagreement.
Maps how work moves between teams and highlights areas of duplicated effort. Grounds discussions about coordination and ownership in concrete examples.
Provides an evidence-backed diagnostic covering capabilities, processes, governance, structure, systems and measures. Gives redesign discussions a basis in actual working practices rather than formal structures alone.
— 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.
Formal structures rarely explain how work actually gets done. Establishing the current operating model is the typical trigger — provides a grounded account of how the organisation works today, supported by quoted evidence from people across teams. Gives advisory teams a shared baseline for operating model discussions. 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 current-state operating model map, with a diagnostic report covering capabilities and work, processes and handoffs, governance and decision rights, structure and roles, systems and data, and measures. 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.
Operating Model Mapper 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.
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.
IT Change Advisory Engine
Reviews a proposed change against your change policy and returns a governed advisory decision — approve, approve with conditions, defer to the change board or reject — weighing risk, blast radius and rollback, with a change manager sign-off required before anything reaches production.