To build a folly is essentially to do something a second time, something at an inopportune moment. That something is always the memory of something forgotten, about which we can paradoxically say "There it is again."
Follies were misunderstood, purposeless constructions. They were often only small, extravagant gestures in a garden, easily whisking off the imagination to distant lands, a sort of time capsule built to awaken the memory and induce surprise in passers-by. They marked locations, organized secondary paths in a park, or simply predicted the arrival of better times—a demarcation, a sacred spot, a mysterious trail, a hill whose tragic rocky nature begged for a tower, a party, or the arrival of summer.
“It is demonstrably true that things cannot be other than as they are. For, everything having been made for a purpose, everything is necessarily for the best purpose.” — Professor Pangloss
I’m concerned with how I witness the work of user experience practitioners getting treated: like it’s just a set of motions toward a product’s all-important implementation, and one that we try to compress, due to its ostensible superfluity. Once the implementation is finished, the UX work appears to usually get discarded.
I submit that the materials that form the precursors to a product’s implementation have considerable value on their own.
My vision is that I will be able to ask a question as mundane as one about the wording of a single button, and trace the answer all the way back to the overarching business strategy to see that it makes sense.
It isn’t a site, or a service, or even an identifiable product at all, but rather a system for creating a skin around and connective tissue between things like:
Demographic studies
Contextual inquiries
Stakeholder and user interviews
Surveys
The business ecosystem
Personas
Scenarios
Sketches, storyboards, wireframes
Mockups, models and prototypes
Email and IM conversations
Meeting notes
Content inventories and audits
Concept schemes, taxonomies, thesauri
A UI style guide
A branding and visual identity guide
A voice and tone guide
A code style guide
...etc
The individual elements of such a corpus represent the work of half a dozen specialist sub-disciplines, and are useful for realizing a product’s implementation. But if you hook them all up together, they merge to become a strategic artifact that transcends products and operates as a critical control surface for the business. This is because what such an artifact represents is a coral reef of deeply-considered and hard-fought decisions, and a story of the process that yielded them.