Church on the Water, Hokkaido, 1985–8 At the edges of the outer walls to left and right, the slate floor is held back, creating a shadowed slot into which the concrete wall slips out of sight. Because the wall does not meet and bear upon the floor, as is usual, the relationship of the wall to the ground is uncertain, and the rippling surface of the black slate floor appears to float free of the walls, merging with the rippling surface of the water. Robert McCarter & Juhani Pallasmaa, Understanding Architecture weight
Lightness & Heaviness "Lightness is born of heaviness and heaviness of lightness, instantaneously and reciprocally, returning creation for creation, gaining strength proportionally as they gain in life, and as much more in life as they gain in motion. They destroy one another also at the same time, fulfilling a mutual vendetta, proof that lightness is created only in conjunction with heaviness, and heaviness only where lightness follows." — Leonardo da Vinci Robert McCarter & Juhani Pallasmaa, Understanding Architecture materialweight
Buttresses Buttresses, Ruskin writes, are structures against pressure: a cathedral’s walls want to fall outward, for example, pushed aside by the relentless weight of the roof. But this gravitational pressure can be stabilized by an exoskeleton: a sequence of buttresses that will prevent those walls from collapsing outward. However, Ruskin points out, there is a similar kind of pressure from the waves of the sea. Think of the curved hull of a ship, he writes, which is internally buttressed against the “crushing force” of the ocean around it. It is a kind of inside-out cathedral. Geoff Manaugh, BLDGBLOG www.bldgblog.com weightarchitecture
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