Function, Functionality, Functionalism
The requirements of economy
Useless work on useful things
The minimum condition
Form eschews function
Feeble and ugly
Functionalism can be a kind of religion
Each element performs many functions
The informing idea of functionalism
Same name in the same basket
The plan must anticipate all that is needed
The element becomes a sign
Classical absurdity
205. Structure Follows Social Spaces
Roaming and capricious
What are those borders made of?
Presentable
A strangely negative character
Sine qua non
The contribution that something in them yet compelled them to make
Something more is required
Mechanisms and organisms
The center of the way
The Evolution of Useful Things
The usages of life
Form follows function
Against form follows function
UI and Capability
Embracing design constraints
An Article by Adrian RoselliConstraints have been shown to generally improve innovation. Giving targets and parameters helps ensure a team is working in unison. Identifying what is out of bounds can further focus that team.
A Plea for Lean Software
An Essay by Niklaus WirthSoftware's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
Beauty in flight
A QuoteAll of us had been trained by Kelly Johnson and believed fanatically in his insistence that an airplane that looked beautiful would fly the same way.
— Ben Rich, Skunk Works
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.