stairs
The precise construction of relationships
This flight of steps runs up the outside of a Modernist house in Switzerland. What is striking here is the precise construction of relationships. The gaps between steps allow crisp lines of light to fall on the darkly shadowed wall, reinforcing the subtlety of the dialogue between granite and the concrete, which has been bush-hammers to expose the stone aggregates.
Thoughts on stairs
...There is something hypnotic about stair climbing, and as often as I find myself thinking I ought to be at the fourth floor when I am only at the third, I think I've only gotten to three when I'm actually arriving at four.
...To my eyes (and legs) the straight run is more elegant and enjoyable to ascend.
...The narrowing is both functional and artistic, acknowledging that a stair is likely to be used by a smaller number of people as it rises and forcing the perspective narrowing of the long view upward.
...The symbolic weight of stairs is embodied in both their form and their magnitude.
They are something that has been buried
A Quote by Le CorbusierFor two and a half months I did not see a stairway in America. They are something that has been buried...hidden behind a door that you are not supposed to open.
Product vs. Feature Teams
This article is certain to upset many people.
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?
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.