Some thoughts on Revit

Some people have to be reminded that the project file is a database and like any database the more and accurate information about the project you put into the model the more analytical modeling and scheduling you can get out of the model.

Building highly parametric families that flex can be just as tedious as software programming if you're not familiar with the "programming language" or in this case the many rules and shortcuts for family file creation. The family editor is in essence a "graphical" programming environment. Being more visual, this is probably the perfect programming enviroment for architects. As a rule of thumb the more automation you want to build into family or project files the more skilled your users have to be to modify these files later. Not everyone in the office needs to understand the rules of family file creation to use these families, but they would need some expertise to open these family files and make significant modifications. I know the same is true for many BIM applications.

Autodesk publishes basic usage of the tools in Revit, but there are many clever things an office can do by mixing and matching different tools and parameter values to get the project file to analyze the database and report and illustrate the information you need (and some information you didn't know you needed).