Work that continues without you

The first time you open this page the number will be bad. Mine was. Almost everything a team makes with AI starts out living with the person who made it, because that is where it was made, and nobody sat down one day and decided to hoard it. The point is not that you have already fixed that. It is that you can finally see it, and watch it move.

So the first number is work that carried on without its owner. Counted rather than assumed. That is the number that tells you whether anything your team built actually belongs to the team, or whether it belongs to whoever is on holiday.

The second is exposure, and it is sharper than a list of who owns what. It is capabilities that one person has mastered and nobody else has reached, because the prerequisites are not met anywhere else on the team. That is the version that hurts when they resign, and it is a different question from who is currently assigned to something.

The third is the one we argue about most and rarely measure. We say your team's work is not tied to whichever AI tool you happen to use. So this counts the skills your team actually uses that two or more tools can reach, against the total in use. Those are the ones that would still be there if somebody changed tools.

Underneath all of it is whether people are connected at all. Never synced, tools per member, completion rate. Continuity of work you have not started is not a problem you have yet.