He documented everything before he left, and most of it went unused

Before a product leader left a company, he spent his last weeks recording walkthroughs of features the company had built and then retired. The reasons had nothing to do with the features themselves. The company still owned the intellectual property and might want to use it later.

Each recording covered the use cases, how to operate the feature, how it was designed and why, and the documentation that went with it. Whoever decided to rebuild would have a running start. The recordings and documentation were stored in the company’s shared folders. The handoff was complete.

A few years later, the company did rebuild. The team used part of one feature and dropped the rest.

Three possible explanations

He has three guesses about why. The rebuild team may not have understood the material. They may not have known it existed. Or they may have looked at it and decided to start fresh.

From outside, all three look the same: a rebuild that starts closer to scratch than it needed to.

When knowledge goes missing at work, the usual explanation is that it stayed in someone’s head. That explanation is often right. Teams lose a great deal to reasoning that one person has and doesn’t write down.

Here, everything was written down, recorded and left where the company could find it.

A record that did get used

Earlier this week I told a story about a guide I wrote to an overnight batch process. For years, the support team opened it from their shared folder every few weeks. A customer would ask about the process, and the team would reference the guide for the answer.

The recordings had no work like that around them. The features were retired, so a normal week gave the team no reason to open them. They waited for a decision to rebuild, and that decision came years later.

A record gets used when it sits in the path of the work someone is already doing.

Where a record for retired work belongs

Customer questions gave the support team a reason to open the guide. For a retired feature, that occasion might come years later, when someone asks to bring it back. By then, the person writing the proposal may be new to the team.

That decision to re-engage is where the record belongs. A handoff for retired work can name the events that would bring the work back, such as a proposal to rebuild the feature or a customer asking for it again, and attach the record to each one. Whoever raises the proposal would get directed to the recordings first.

In practice, that is a note on the retired feature in the backlog, or a step in the template the team uses to propose new work.

The person who takes up the work has the benefit of the thinking and can decide for themselves.

Resources, Not More Work