Evolution & Change
Form follows failure
Deliberate acts
It must constantly be re-created
Big things and little things
To evolve the language itself
A gradual refinement
Mechanisms and organisms
"Kant described a mechanism as a functional unity, in which the parts exist for one another in the performance of a particular function.
An organism, on the other hand, is a functional and structural unity in which the parts exist for and by means of one another in the expression of a particular nature.
This means that the parts of an organism – leaves, roots, flowers, limbs, eyes, heart, brain – are not made independently and then assembled, as in a machine, but arise as a result of interactions within the developing organism."
— Brian Goodwin, How the Leopard Changed His Spots
Stepping stones in possibility space
An Article by Gordon BranderIf we try to cross this lake by following only the stepping stones that lead toward our objective, we’ll soon get stuck. But what if we let go of our objectives? What if we focused on trying to find new stepping stones instead? This is novelty search. Instead of looking for something specific, you look for something new.
Novelty search isn’t just random, it’s chance plus memory. Together, these ingredients do something interesting.
...Stepping stones are also combinatorial. Each new stepping stone we discover expands our potential to find even more stepping stones. Collecting stepping stones is a luck maximization algorithm. By collecting and combining stepping stones, we might arrive at our destination by accident, or somewhere more interesting!
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.