Patterns are simply another tool at our disposal. Second, patterns only add value if they are practiced consistently over time. Just capturing patterns for one application is hardly worth the trouble. Application architects must establish the infrastructure for patterns, creating standard mechanisms to capture and maintain the patterns over the long haul, refining patterns when necessary. For instance, the vocabulary should be the same across many projects, or there is no need to create a standard vocabulary.
Consistency is key.
What's more, patterns should be accesible by all members of the application development teams, and all members should be trained in their use. Finally, patterns only provide an opportunity for reuse, not a guarantee. There is a difference. Furthermore, patterns don't need rigorous notation, a rigid process, or expensive tools. You can just as easily capture patterns on index cards or using a word procesor.