We are a small firm. This concept may not apply to large firms that have learned how to enforce strict policy. I would also not be surprised to hear that this has been said before, in one form or another, but here goes.
I’ve been writing and implementing dynamo scripts in our office for the past two years. It seems to be that in my experience, there are at least three classes of dynamo script: Class A, Class B, and Class C. And I don’t really know which class of script I am writing until the project is done.
Class A scripts are for all users. The script can run in dynamo player and saves the user time. There is no requirement that says everyone has to use this script. If a user wants to save time and effort it is entirely up to them.
Class B scripts I build to better myself. They are often very complicated, may require tweeking between Revit versions, and may or may not run in dynamo player. Users typically come to me when they want me to run this script on their project. Class B scripts can extend a users skill set beyond that of the common draftsman, but I wouldn’t ask anyone else on staff to run them.
Class C scripts usually end up on the cutting room floor, or archived for future reference. They may do a great thing, that the users have been asking for, but to be useful they must be run constantly by all users on a project all the time (https://goo.gl/9uZNHL). That’s just not going to happen in a small office. Most users are still learning Revit and often refuse to run dynamo and even dynamo player, as simple as it is.
I always try to build the Class A script, I appreciate the personal and professional benefits of the Class B script, and I have hope for the Class C script, that perhaps one day its time will come.