The reality of the building One day I went to my study at Taliesen to sit down and rest. I picked up a little book just received from the ambassador to America from Japan. It was called The Book of Tea by Okakura Kakuzo. I wonder how many of you have read it? Well, in that little book I came upon quotations from the great Chinese poet-prophet Laotze, things he had said five hundred years before Jesus. As I turned the pages I suddenly came across this: "The reality of the building does not consist in the four walls and the roof but in the space within to be lived in..." The answer is, reality is the space within, into which you can put something. In other words, the idea. And so it is with architecture; so it is with your lives; and so it is with everything you can experience as reality. You will soon find out for yourselves if you begin to work with this principle in mind, that things will open to you...Therein lies the secret of great peace, missing in Western Civilization today. Frank Lloyd Wright, The Book of Tea space
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