The Third Way An Article by Kevin Kelly kk.org But all the civilized cities of the world were also filled with third places that people loved. Not quite private, not quite public, these third places were intimate but open to anyone. Like settling down at a table at a cafe. It felt like your space, but you were not the landlord. They were public, open spaces that you could “own” for a while. …We need a new third category of work — something between “employee” and “not an employee”—that encompasses digital gig laborers. AirBnB is neither a hotel, nor a private resident. It is a third thing, and we need to create a new category to deal with it…This is the era of the third way. placesocietyworkculture
Class 1 / Class 2 Problems An Article by Kevin Kelly kk.org There are two classes of problems caused by new technology. Class 1 problems are due to it not working perfectly. Class 2 problems are due to it working perfectly. ...Class 1 problems arise early and they are easy to imagine. Usually market forces will solve them. You could say, most Class 1 problems are solved along the way as they rush to become Class 2 problems. Class 2 problems are much harder to solve because they require more than just the invisible hand of the market to overcome them. ...Class 1 problems are caused by technology that is not perfect, and are solved by the marketplace. Class 2 problems are caused by technology that is perfect, and must be solved by extra-market forces such as cultural norms, regulation, and social imagination. problemstechnologyculturesociety
1,000 True Fans An Essay by Kevin Kelly kk.org To be a successful creator you don’t need millions. You don’t need millions of dollars or millions of customers, millions of clients or millions of fans. To make a living as a craftsperson, photographer, musician, designer, author, animator, app maker, entrepreneur, or inventor you need only thousands of true fans. A true fan is defined as a fan that will buy anything you produce. These diehard fans will drive 200 miles to see you sing; they will buy the hardback and paperback and audible versions of your book; they will purchase your next figurine sight unseen; they will pay for the “best-of” DVD version of your free youtube channel; they will come to your chef’s table once a month. If you have roughly a thousand of true fans like this (also known as super fans), you can make a living — if you are content to make a living but not a fortune. artmakingfame
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