I’ve actually been trying to get our product and development teams on board with doing “rich” specs like these. I’ve found a couple sticking points: people tend to believe the extra detail isn’t necessary (against which I argue, how can we design and develop that extra detail if it’s left out of the documentation process entirely), the process is too time consuming (against which I argue that the time is worthwhile and probably not much more than we spend on “flat” specs now), and, finally, that people may not have the background to pull these specs off. It’s this last point that I can’t counterargue.

Working in a very mixed environment where the spec-writers may not have design or development backgrounds, I find that the biggest sticking point to introducing rich specifications is that people are afraid to believe that their design - PPT - HTML - Photoshop - (heck, even Paint) skills are good enough to do prototypes or specs like these. People are reluctant to enter the imagined world of the “designer” or “developer” - “the only people with the skills to do these things” - which makes them reluctant to produce the high-quality documents that you and I believe should be produced throughout a project process.

The low fi animations shouldn’t take long to make, btw. I’ve made them in 20 minutes with animated gifs.