water
Watermill
Rain Chains & Musical Drains
A rain chain in winter; Dresden Kunsthof Passage; Drainage planters near Pike Place Market in Seattle.
If there is a larger takeaway here perhaps it is about paths of least resistance, with regards to both the actual flow of water and design decisions. On the one hand, it is easy to blindly follow regional precedents and traditions with long histories (or grab whatever is handy at the hardware store). On the other hand, sometimes it makes sense to take a step back and decide consciously how to reveal (or conceal) a natural process.
The Beauty of the Overlooked
An Article by Maria PopovaMedusa from A Naturalist’s Rambles on the Devonshire Coast by Philip Henry Gosse, 1853.
Philip Henry Gosse’s Stunning 19th-Century Illustrations of Coastal Creatures and Reflections on the Delicate Kinship of Life
“These objects are, it is true, among the humblest of creatures that are endowed with organic life… Here we catch the first kindling of that spark, which glows into so noble a flame in the Aristotles, the Newtons, and the Miltons of our heaven-gazing race.”
Rain chains
An ObjectRain chains are a beautiful and functional alternative to traditional, closed gutter downspouts. Guiding rain water visibly down chains or cups from the roof to the ground, rain chains transform a plain gutter downspout into a pleasing water feature. From the soft tinkling of individual droplets to the soothing rush of white water, they are a treat to listen to.
Rain chains (‘kusari doi’ in Japanese) in concept are not a new idea. For hundreds of years, the Japanese have used the roof of their homes to collect water, transporting it downward with chains and finally depositing the rain water into large barrels for household water usage. Japanese temples often incorporate quite ornate and large rain chains into their design.
Skeleton, Organs, Circulation, Sinew, Skin
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.
Tracing the answer back
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.
The UX coral reef
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
...etcThe 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.