World Model Readiness
Engraved team-practice instrument

For your team

Team Practice

Module · Where automation breaks at the seams

The Cross-Team Handoff Check

AI speeds up what happens inside each team, then everything slows down at the handoff. The seams between teams are where automated output meets a different format, a different owner, and a different set of assumptions. This module checks the five that decide whether work flows across the boundary or piles up on it: interface clarity, format fit, who owns the seam, how errors route back, and whether anyone can see the whole path.

Question 1 of 5 · The interface is defined

When your team hands work to another, is it clear exactly what they expect?

The other team has a shape they need: fields, order, level of detail, definitions. If that shape lives in habit rather than in writing, every AI-generated handoff is a guess, and guesses drift.

Question 2 of 5 · Formats actually fit

Does AI-generated work arrive in a form the receiving team can use as is?

AI is fluent at producing almost-right formats: the near-miss spreadsheet, the summary that reads well but drops the field downstream depends on. Someone reformats it by hand, and the automation's time saving quietly leaks away at the seam.

Question 3 of 5 · The seam has an owner

Does anyone own the handoff itself, or only the two teams on either side?

Each team owns its own work and assumes the seam is the other team's problem. The gap between them is where things fall through, precisely because it belongs to no one. Automation widens that gap by moving work through it faster.

Question 4 of 5 · Errors route back fast

When a handoff arrives wrong, does the receiving team know where to send it back?

An error caught downstream needs a fast path back to whoever, or whatever, produced it. Without one, the receiving team silently fixes it themselves, the source never learns, and the same error arrives again next week.

Question 5 of 5 · The whole path is visible

Can anyone see a piece of work travel from your team to its final destination?

Each team sees its own leg. Nobody watches the relay. When AI speeds up the individual legs, the delays and drop-offs move to the handoffs, exactly where no single team is looking.

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.

How many other teams does your team hand work to or receive it from regularly?

One
Two or three
Four to six
More than six
Never counted

Where does cross-team work most often stall today?

Wrong format on arrival
Nobody owns the seam
Errors with no way back
Nobody sees the whole path
It rarely stalls

How automated is the handoff between your team and the next?

Fully manual
AI drafts, humans pass it on
Partly automated seam
Mostly automated seam
Not sure

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.

The interface is defined

  1. 1Nobody agreed it
  2. 2Learned by habit
  3. 3Verbal understanding
  4. 4Written interface
  5. 5Written and versioned

At the low end: An undefined interface means each side assumes a different one, and AI makes the mismatch faster. Write down what the receiving team actually needs, in their words, this week. What good looks like: A written, versioned interface is what lets both sides automate without breaking each other. Review it when either team changes its tools; the contract has to keep up with the machinery.

Formats actually fit

  1. 1Always reworked
  2. 2Heavy reformatting
  3. 3Some cleanup
  4. 4Usually fits
  5. 5Fits by design

At the low end: If every handoff is reworked before it is usable, the automation upstream is creating work downstream. Fix the output shape at the source so it lands ready to use. What good looks like: Output that fits by design is what makes cross-team automation actually pay. Keep the generating prompt and the receiving format in sync; a change on either side reopens the gap.

The seam has an owner

  1. 1Belongs to no one
  2. 2Both sides blame
  3. 3Owned in a crisis
  4. 4One side owns it
  5. 5Jointly owned, named

At the low end: A seam nobody owns is where work goes to disappear. Name one person accountable for the handoff working end to end, even if they sit on only one side of it. What good looks like: A jointly owned, named seam is rare and valuable. Keep the owner close to the interface definition so the contract and the accountability stay in the same hands.

Errors route back fast

  1. 1Silently fixed downstream
  2. 2Complained about, not routed
  3. 3Ad hoc email back
  4. 4Known return path
  5. 5Routed and tracked

At the low end: When the downstream team quietly fixes upstream errors, the source never improves and the cost hides forever. Open one named return path so mistakes go back to where they were made. What good looks like: A tracked return path turns cross-team errors into cross-team learning. Watch the return volume by type; a spike is usually a tool or a prompt that changed upstream without telling anyone.

The whole path is visible

  1. 1Each sees its leg
  2. 2Pieced together after
  3. 3Visible on request
  4. 4End-to-end for some
  5. 5End-to-end, live

At the low end: If no one can see the whole path, no one can find where work stalls between teams. Map one end-to-end flow by hand; the handoffs you cannot see are where the time goes. What good looks like: End-to-end visibility is what lets you manage the seams instead of just the teams. Extend it to the flows that matter most and watch the handoff times; that is where automation pays or leaks.