World Model Readiness
Engraved team-practice instrument

For your team

Team Practice

Module · Inside the work, or beside it

The Team AI Workflow Check

The gap between a team that got value from AI and one that just bought licences is almost always the same: whether the AI sits inside the daily workflow or off to the side in a separate tab. AI beside the work adds steps, creates handoffs, and quietly duplicates effort. AI inside the work removes friction and gives time back. This module checks the five things that decide which one you have: whether AI lives in the tools your team already uses, how much friction sits at the handoffs, whether AI and people are redoing each other's work, who owns the workflow, and whether you can actually measure the time it saves.

Question 1 of 5 · AI is in the tools

Does AI live inside the tools your team already uses, or in a separate tab?

AI that lives in its own window is AI your team has to remember to go and use, and mostly they will not. Value shows up when the AI is inside the inbox, the document, the ticket, the place the work already happens. Integration is not a technical nicety; it is the difference between a tool that gets used and one that gets forgotten.

Question 2 of 5 · Handoffs are smooth

When work passes between AI and people, how much friction is there?

Every handoff between a person and an AI is a place where context gets lost, formats do not match, and someone has to reshape the output before the next step. Smooth handoffs make the AI feel like a teammate; rough ones make it feel like extra work with a middleman. The friction at the seams is where the promised time savings quietly leak away.

Question 3 of 5 · No duplicated work

Are your people and your AI quietly redoing each other's work?

A common failure is invisible: the AI drafts it, then a person rewrites it from scratch, or two people both check what the AI already produced. The tool was supposed to save effort and instead added a parallel track. If nobody has looked, assume some of this is happening, because it usually is.

Question 4 of 5 · Workflow has an owner

Does anyone actually own how AI fits into your team's workflow?

An AI workflow that nobody owns is one that nobody improves. It gets set up once, drifts as tools and needs change, and slowly decays while everyone assumes someone else is tending it. A named owner is the difference between a workflow that gets better and one that quietly rots.

Question 5 of 5 · Time savings measured

Can you show the time AI actually saves your team, or just claim it?

Almost every team assumes its AI tools save time; far fewer have measured it. Without a number, you cannot tell a genuine win from a comfortable belief, you cannot justify the spend, and you cannot find the workflows where the AI is actually costing time. A rough measured figure beats a confident guess every time.

For the statistics · one click each

Three questions for the public picture

These do not affect your score. They feed the anonymised, aggregated statistics; groups under 8 respondents are never shown.

Where does AI sit relative to your team's daily tools?

A separate tab
Copy-paste between tools
Inside the main tools
Native to the workflow
We do not use AI yet

Who owns how AI fits into your team's workflow?

Nobody
Unclear
A named person
An owner actively improving it
Not sure

Have you measured the time AI saves your team?

Never measured
Anecdotes only
Rough estimates
Measured properly
No AI in the workflow

Your context

Used to calibrate the report. Company size and sector remain in the anonymized dataset; your email does not.

What the five levels look like

Every dimension in this assessment is scored 1 to 5. This is what the levels mean, dimension by dimension. The graded report diagnoses where your own answers land and what to do about it.

AI is in the tools

  1. 1Separate tab only
  2. 2Copy-paste between
  3. 3Some integration
  4. 4In the main tools
  5. 5Native to the workflow

At the low end: AI in a separate tab is AI your team has to remember to visit, which means most of the time they will not. Get it into the one or two tools where the work actually happens, and adoption follows. What good looks like: AI native to the workflow is AI people use without thinking about it, which is the whole point. Keep it embedded as tools change; an integration that breaks silently sends everyone back to the tab.

Handoffs are smooth

  1. 1Constant reformatting
  2. 2Rough handoffs
  3. 3Some friction
  4. 4Mostly smooth
  5. 5Seamless handoffs

At the low end: If every handoff means reformatting and reshaping, the AI is creating work at the seams even as it saves it in the middle. Fix the roughest handoff first; that is where the time is leaking. What good looks like: Seamless handoffs make AI feel like part of the team rather than a step to manage. Keep watching the seams as workflows change; new friction loves to hide at a handoff.

No duplicated work

  1. 1Heavy duplication
  2. 2Often redone
  3. 3Some overlap
  4. 4Little duplication
  5. 5Clean division of labour

At the low end: When people routinely redo what the AI produced, you are paying twice and saving nothing. Watch one workflow end to end and find where the effort is being duplicated, then cut one side. What good looks like: A clean division of labour between people and AI is where the real time savings live. Revisit it as the AI improves; work that needed a human check last quarter may not need it now.

Workflow has an owner

  1. 1Nobody owns
  2. 2Owner unclear
  3. 3Loosely owned
  4. 4Clear owner
  5. 5Owner, actively improving

At the low end: An AI workflow with no owner is one that was set up once and left to rot. Name someone responsible for how AI fits the team's work, with the remit to change it. What good looks like: An owner actively improving the workflow is what keeps AI value growing instead of decaying. Keep that ownership funded with real time; a workflow owner with no hours is a title, not a role.

Time savings measured

  1. 1Never measured
  2. 2Anecdotes only
  3. 3Rough estimates
  4. 4Measured somewhere
  5. 5Measured, acted on

At the low end: If you have never measured the time AI saves, you cannot tell a real win from wishful thinking. Pick one workflow and time it with and without the AI; the answer will tell you where to invest. What good looks like: Measured time savings that you act on is how AI stops being an act of faith and becomes a managed investment. Keep measuring as the tools change; last year's win can quietly become this year's wash.