01 · The problem
Twenty programs, all going stale
There are about twenty programs going at any time. What anyone knew about them lived in decks, documents, shared drives and people's heads, and every copy started going out of date the day someone stopped tending it. Nobody had time to tend all of it.
A year of keeping twenty programs current
Each card is one program. The orange is how current its page is. Drag through the year, then switch how the upkeep happens.
02 · The approach
Feed it as things happen
When something changes on a program, we hand the new information to Claude to ingest. Custom Claude Code skills write it into the right pages, look for gaps, and draw D3 maps of how the programs connect. We review what it wrote before we call a page updated.
I track every program's movement in a Power App. When one goes quiet long enough to count as stale, I look at it and make a call: update it, leave it as it is, or close it out. Closed programs move to an archive, and Claude can still pull from them when an old question comes back.
The wiki is organized around how people actually search, not around the org chart. My team keeps it, and leadership reads it when they need to know where a program stands.
The rest is password protected
The full study shows the skills, the tracker and how a program gets called stale, the D3 views, and what changed for the people who use it.
Request access Enter password