If you have ever written a Functional Spec...

... you may find this little article very interesting. I have always created little screens and flows - visitor experiences - to help our clients understand the purpose of the interface and to put a 'timeline' to the functionality. Specs, while I have always thought them necessary, too often lead to a simple project becoming a huge, overly specced project.

Getting Real, Step 1: No Functional Spec (Signal vs. Noise): "Getting Real is all about starting from the user interface and customer experience and then building out. Visual design first, programming second. The more traditional process is starting from the abstract (documentation, diagrams, charts, etc.), coding a skeleton app, and then homing in on the real by finishing it up with an interface. We think that's backwards."