Models and documentation
Schools and universities are often troubled to teach new, working models. If we're careful enough, we might find models that are taught there ten years after their initial appearance. People that accept them with no doubt are affected in two ways: (1) they learn what was before, so (2) they have no time to learn what is now.
I try to follow only models that are immediately useful. Some may have indirect advantages or work only in a particular domain. Once the domain changes, they become useless. Different domains have different requirements, so a model that works for one may not work for another.
Documentation facilitates discussion and innovation when a variety of people work together. It should be written in advance of our intentions, otherwise we'll forget to describe fully what we did. A user requirements documentation can serve as a contract between a client and a company.