The allure of clicks If more of us, as designers, approach what we encounter on design aggregators every day in this way, perhaps we can begin to effect some structural change. By and large these sites are just as susceptible to the allure of clicks as the craft of design. But if we are more selective about what we consume, we may be able to encourage design publications to follow that lead by applying editorial judgment to what gets shared every day. Khoi Vinh, Design Discourse is in a State of Arrested Development www.fastcompany.com consumption
From consumption to production I see no other solution (political, economic) to the problems of mankind than the formation of small responsible communities involved in permaculture and appropriate technology. I believe that the days of centralised power are numbered, and that a re-tribalisation of society is an inevitable, if sometimes painful, process. The greatest change we need to make is from consumption to production, even if on a small scale, in our own gardens. Bill Mollison, Introduction to Permaculture societyconsumptionproduction
High-priced good times Once again, a neighborhood dedicated to production has been transformed into one for consumption. As someone who believes that an internal balance between these activities is vital to the health, character, and autonomy of the city, I find that the sight of yet another zone of high-priced good times gives me the willies, even as I tuck into my perfect branzino in the lovely back garden of the delightful Italian restaurant. Michael Sorkin, 20 Minutes in Manhattan consumption
What premium mediocre is not So premium mediocrity is not clueless, tasteless consumption of mediocrity under the mistaken impression that it is actual luxury consumption. Maya Millennial is aware that what she is consuming is mediocre at its core, and only “premium” in some peripheral (and importantly, cheap, such as French-for-no-reason branding) ways. But she consumes it anyway. She is aware that her consumption is tasteless, yet she pretends it is tasteful anyway. Second the distinguishing feature is that premium mediocrity only signals an appearance of striving upwards. Everybody in the premium mediocre world recognizes that it is not a reliable indicator of actual upward striving, such as number of code commits on github, or non-bot retweets achieved by on a tweet. In other words, premium mediocrity is dressing for the lifestyle you’re supposed to want, in order to hold on to the lifestyle you can actually afford — for now — while trying to engineer a stroke of luck. Venkatesh Rao, Premium Mediocre www.ribbonfarm.com consumption
Consumption The proponents of technology in the 1840s were very enthusiastic about replacing workers with machines. But somehow I find no indication that they realized that while production could be carried out with few workers and still run to high outputs, buyers would be needed for those outputs. The realization that though the need for workers decreased, the need for purchasers could increase, did not seem to be part of the discourse on the machinery question. Since then, however, technology and its promoters have had to create a social institution – the consumer – in order to deal with the increasingly tricky problem that machines can produce but it is usually people who consume. Ursula M. Franklin, The Real World of Technology consumptionwastesociety
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