251. Different Chairs Problem People are different sizes; they sit in different ways. And yet there is a tendency in modern times to make all chairs alike. Solution Never furnish any place with chairs that are identically the same. Choose a variety of different chairs, some big, some small, some softer than others, some rockers, some very old, some new, with arms, without arms, some wicker, some wood, some cloth. Christopher Alexander, Murray Silverstein & Sara Ishikawa, A Pattern Language Drawing pictures of citiesAn index of the shifting patterns furniture
An index of the shifting patterns "Because this is a garden where things can be left out at night without being stolen, we're going to 'furnish' the garden with French café chairs that won't be secured in the ground, so people can move them to wherever they want to sit...It's like with the chairs being totally casual and relaxed and comfortable. They set a tone. There's things that you have to do to get the right feel, where it's all already there, but then, you know, 'Bing!' – there's a moment of recognition." The patterning of chairs pulled together in different ways by successive waves of visitors over the course of the day becomes an index of the shifting patterns of people that sit in a variety of arrangements to facilitate conversations and other intersubjective alignments, or simply to allow for a moment of private contemplation free from contact with others. Matthew Simms, Robert Irwin: A Conditional Art 251. Different Chairs furniture
From the desk of A Blog by Kate Donnelly fromyourdesks.com A site dedicated solely to canvas of the Desk. A Desk is where we work. Symbolic. Physical. Present. A second and third home. A Desk is a platform. A hearth. Roots are planted. It’s a place, a sanctuary, where hours upon hours pass. From the desk of: Austin Kleon workfurniture
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