Blessed by the four elements The Indian stone temple also included, in its architectural form, the means for being blessed by the four elements—earth, wind, water, fire. Before entering the temple gates, one removed one's shoes to touch and be blessed by the earth. Then upon passing through the temple gateway, one is blessed by the air with a gust of wind. A blessing by water is obtained by bathing in the temple tank, or at least descending its steps to touch the water. Finally, on entering the cool interior of the sanctuary, the worshipper is given a mark on the forehead with ashes taken from a sacred flame by an attendant priest. Even this blessing by fire has a slight cooling sensation to it. Perhaps it is only coincidental that each of these four blessings is associated with a cooling sensation; and yet, the use of forms and materials that inevitably create coolness is quite remarkable. Lisa Heschong, Thermal Delight in Architecture Avatar: The Last AirbenderThe Legend of KorraA hierarchical system of sense elements
A hierarchical system of sense During the Renaissance, the five senses were understood to form a hierarchical system from the highest sense of vision down to touch. Vision was correlated to fire and light, hearing to air, smell to vapour, taste to water, and touch to earth. Juhani Pallasmaa, The Eyes of the Skin: Architecture and the Senses Avatar: The Last AirbenderPrometheusBlessed by the four elements fireelementssenses
Avatar: The Last Airbender A Series The Legend of KorraBlessed by the four elementsA hierarchical system of sense spiritelements
The Legend of Korra A Series If you look for the lightWhen we hit our lowest point Avatar: The Last AirbenderBlessed by the four elements spiritelements
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