Together we followed a Design Fiction approach to produce a Quick Start Guide for a technology that could substantially change mobility in the future. First, over the course of four hours we identified the key systems and the FAQs that implicate the human aspects of a self-driving car. For each key system, we illustrated the interaction, described the system and the steps for its use. The FAQs represented what we determined might be questions raised by the new self-driving car owner. Using the Quick Start Guide format as a Design Fiction archetype provided a way to focus the workshop discussion in order to identify topics that may not come up when discussing the larger system. It also forced us to create rather than just debate, and represent topics concisely to focus the work and challenge us to describe features succinctly.

This Quick Start Guide Design Fiction archetype is a natural way to focus on the human experiences around complicated systems. The Quick Start Guide implies a larger ecosystem that indeed may be quite complex. It also allows one to raise a topic of concern without resolving it completely — often an approach that's necessary in order to not be bogged down in details before it's necessary. For example, mentioning that it costs more to park your car rather than sending it back on the roadway as a taxi is a way to open a conversation about such a possibility and its implications for reclaiming space used by parking garages.

In a short amount of time, we brought to life such experiences in a very tangible, compelling fashion for designers, engineers, gurus, and anyone else involved in the development of a technology. The QSG became a totem through which we can discuss the consequences, raise design considerations and hopefully shape decision making. This approach leads to better thinking around new products, a richer story and good, positive, creative work.

Visions of exciting future things rarely look at the normal, ordinary, everyday aspects of what life will be like to turn the thing on, fix a data leak, set a preference, manage subscriber settings, address a bandwidth problem, initiate a warranty request for a chipped screen or increase storage. It’s those everyday experiences — after the gloss of the new purchase has worn off — that tell a rich story about life with a self-driving vehicle. In this project, we made a few category assumptions.

First, the self-driving vehicle is all about the data. When Amazon, Facebook, Microsoft, Google and/or Apple become part of the vehicle “ecosystem” — either by making cars, having their operating system integral to the car, owning roadways or whatever their strategy teams are dreaming up — they will do it because #data. To them it will be about knowing who is going where, when they’re going there, to get what; it will be about knowing when your tires are wearing down; it will be to give you discounts when send your car to get Pizza Hut for dinner; it will be to have your car go through the Amazon Pantry Pickup Warehouse to do your grocery shopping. The data.

Second, as fundamental as mobility is to humans, owning a network of millions of interoperable vehicles is big business. Apple’s vehicle ecosystem will be always moving, as will Google-Uber’s. It will cost you more to park your self-driving car because it can earn money for them (and maybe you) by putting it into “Taxi” or “Uber” mode when it’s dropped you off at work. This led us to consider what one might need to do if one’s car has strangers in it while you’re at work, or the movies, or asleep. And what will happen to all those parking garages?

Third, roadways will be the new platform play. How will (or will not) roadways that are owned by Amazon, Facebook, Microsoft, Google and/or Apple interoperate? Will Google have the best, fastest, least congested roadways in Los Angeles? What are the consequences of switching to semi-partial manual drive mode? What happens when those Fast and Furious guys figure out how to jailbreak their vehicle’s OS and supercode the engine?