By the handling of human hands This type of beauty grows with each passing day. Utilitarian craftwares become more beautiful the more they are used, and the more beautiful they become, the more they are used. Moreover, the heavens have ordained that these objects should attain an even greater beauty as they become worn by the handling of human hands. Yanagi Sōetsu, The Beauty of Miscellaneous Things Putting Thought Into Things utility
Our aesthetic sense has been severely impaired Until now we have been taught that the right way to appreciate beauty is through visual perception. Utilitarian crafts have been looked down on as something of a lower rank. As a result, our aesthetic sense has been severely impaired owing to the fact that beauty and life are treated as separate realms of being. Yanagi Sōetsu, What is Folk Craft? utility
Primary uses Any primary use whatever, by itself is relatively ineffectual as a creator of city diversity. If it is combined with another primary use that brings people in and out and puts them on the street at the same time, nothing has been accomplished. In practical terms, we cannot even call these differing primary uses. Jane Jacobs, The Death and Life of Great American Cities utility
Wide sidewalks The narrower the sidewalks, the more sedentary incidental play becomes. Sidewalks thirty or thirty-five feet wide can accommodate virtually any demand of incidental play put upon them—along with trees to shade the activities, and sufficient space for pedestrian circulation and adult public sidewalk life and loitering. Few sidewalks of this luxurious width can be found. Sidewalk width is invariably sacrificed for vehicular width, partly because city sidewalks are conventionally considered to be purely space for pedestrian travel and access to buildings. Jane Jacobs, The Death and Life of Great American Cities utility
Hacking is the opposite of marketing An Article by Tom MacWright macwright.com One of my favorite definitions of “hacking” is the creative reuse of tools for new and unexpected purposes. Hacking is using your email account as a hard drive, using your bicycle seat to open a beer, using Minecraft’s red bricks to create a calculator in the game. The opposite of hacking is marketing. Marketing tells you that this particular non-stick pan is the pan you’ll use to make omelettes, and you’ll do it in the morning dressed in fashionable clothing in a nice kitchen. It includes a photo and inspirational copywriting to drive this home. Marketing dictates a style, context, and purpose for even the most general-purpose products. This narrative needs to be specific so that you can readily imagine it: it’s you, in an Airbnb, laughing with friends. All sorts of ways to use the machineIn ways you didn't anticipateStretching the product toolsadvertisingcreativityutility
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility