Freedomless freedom The beauty of kasuri is received as a gift. As long as the laws of nature are upheld, the beauty of kasuri remains intact. This demonstrates the curious principle that the artisan is deprived of technical freedom but works in the freedom of nature. In this sense, kasuri can be said to be created in a state of freedomless freedom. Yanagi Sōetsu, The Beauty of Kasuri freedomconstraintsnaturemaking
Technological middle age In the automobile's technological middle age, it is hard, if not impossible, to tune or repair one's own vehicle. Technical standardization of cars has occurred, and with it the elimination of the user's access to the machine itself. At the same time, the infrastructures that once served those who did not use automobiles atrophied and vanished. Some may say they were deliberately starved out. Railways gave way to more and more roadways. And thus a technology that had been perceived to liberate its users began to enslave them. Ursula M. Franklin, The Real World of Technology technologyfreedominfrastructure
Why We Build the Wall A Song by Anaïs Mitchell genius.com What do we have that they should want? We have a wall to work upon We have work and they have none And our work is never done And the war is never won The enemy is poverty And the wall keeps out the enemy And we build the wall to keep us free That’s why we build the wall We build the wall to keep us free So that its destruction cannot begin workfreedomcapitalism
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