I think you misunderstood my re-documenting comment. You are referring to assets. I'm referring to things like lessons learned and new systems developed. Propri

I think you misunderstood my re-documenting comment. You are referring to assets. I'm referring to things like lessons learned and new systems developed. Proprietary organization is one of the simplest forms this takes. Reinventing even that is a waste of time. I can also tell some of this is getting into specific case territory. :-) For example, sure, I might not bother referencing a simple component. But that's more like "just Google it" territory. No depth. I have lots of master frameworks that are very deep that I'd never want to repeat. DRY is a life saver there. Those files are also more likely to stay put... For your moving links scenario, I use search alongside my organization hierarchy and the links double as search prompts. So that's not a problem. I think this is another case where the specifics matter.