Replication
Reproducing a successful result in a new setting by a different team. It is not copying: it means carrying over the capability and learning, so the second attempt costs less in learning.
Replication is how a one-off success becomes a capability: a different team, in a different context, achieves the useful result. It is not the same as copying. Copying reproduces the surface, such as the prompts, the dashboard or the process, and often misses the reasons they worked.
A second attempt should be cheaper in learning, not just in cost. The team should not have to rediscover what the first one learned, and should also adapt the idea to its own conditions. If a replicated result needs the first team's constant presence, it has not really been replicated.
What helps
- Capture decisions and reasons, not only artifacts.
- Run a second-team test to see what transfers.
- Log and classify rescue work.
- Watch support decay: the help required should fall.
A capability should survive its founders. Replication is the evidence that it does.
Read more in The second team is the real innovation test.
Related terms
Second-team test
A test of whether a different competent team can reproduce a pilot's useful result without inheriting the first team's exceptional conditions or constant expert help.
Rescue work
The extra, often unrecorded help a second team needs from the original team to get a transferred capability working. Classifying it shows what the capability really depends on.
Support decay
The fall in exceptional help a transferred capability needs from its original team over time — the real measure of whether an AI pilot has become an organizational capability.