Moving Beyond Design Thinking

This has to be one of the clearest articulations of Design Thinking I’ve come across in a while. In the course of talking about moving beyond Design Thinking to something the authors call “intervention”, they do an excellent job of embedding an explanation in the context of how it should be used and built upon.

The principles of this approach are clear and consistent. Intervention is a multistep process—consisting of many small steps, not a few big ones. Along the entire journey interactions with the users of a complex artifact are essential to weeding out bad designs and building confidence in the success of good ones.

Slipped Crown

Stephen Johnson zeroes in on some of the challenges using the Apple Watch, and specifically the Digital Crown (the main controller for the device, which sits on the side like an analog watch). I don’t own one, nor have I had an opportunity to use one.

Johnson seems to have nailed the problem by observing that there’s no safe place for a user to navigate to and “reset”. For a lot of users, and especially those who are just learning, memorable linear pathways from a consistent starting point are what they want. Like learning a city subway stop by subway stop, once those pathways have been learned, users can branch out and discover new features.

I’m always fascinated by how product decisions get made, and in this case, how Apple may have compromised their usual clarity when it came to defining the behavior of a critical interface element. I don’t know if this anything more than a stumble for Apple, a sign of them letting technological complexity get out of hand and dictate the user experience. It is certainly intentional and on the other hand may reflect a new outlook for how Apple approaches user experiences.

Interaction Design and Sci-Fi

I recently had the pleasure of speaking to Prof. Robert Thomas’ Collaborative Design For Innovation class at Georgetown University. The curriculum is fantastic – something I could keep studying for a long time – and Robert and his class were welcoming and attentive. Afterwards, one of the students I was speaking with noted that I had listed a number of fiction – science fiction in particular  – works in my annual reading list, and asked why.

At the very core of their practice, designers are clearly tasked with imagining the future state of a product or service. Herb Simon said that “The process of design is a continual cycle of generating alternatives and testing to evaluate them.” I’ve always had a fondness for speculative fiction, and it informs my ability to create and iterate solutions by training my mind to think beyond present realities and imagine different ways of doing things, big and small. When I was in graduate school at Carnegie Mellon’s School of Design, Neal Stephenson’s Diamond Age was required reading. One of the greatest science fiction authors, Arthur C. Clarke, was also credited with inventing a number of significant scientific breakthroughs. In much the same way, I enjoy traveling to different countries where I can experience a significant culture shock.

I highly recommend that designers read science fiction periodically. It doesn’t need to be stereotypical rockets-and-lasers stuff, either: there’s quite a bit of work being produced today that is excellent. I came across a few readings related to this that might be worth digging into for more inspiration:

Why Todays Inventors Need To Read More Science Fiction and mentioned in there is Sophia Bruekner’s class on scifi 

Make It So: Interaction Design Lessons from Science Fiction

2014 Reading List

A good year for fiction, especially of the science variety. I thoroughly enjoyed The Moor’s Account based on both the concept of the book as well as the story itself. I especially enjoy how Ian McEwan paints his characters, and The Children Act did not let me down. The Sixth Extinction was less in depth and more accessible than Elizabeth Kolbert’s New Yorker articles, but the breadth captures the scope of the disaster humans are making of the planet. The Serial podcast was memorable for its storytelling, although it ended up putting a big dent in my reading time.


The Children Act
Ian McEwan

The Son
Philipp Meyer

All the Light We Cannot See
Anthony Doerr

The Moor’s Account
Laila Lalami

Station Eleven
Emily St. John Mandel

The Book of Strange New Things
Michel Faber

Howard Jacobson

Gone Girl
Gillian Flynn

Tenth of December
George Saunders

On Such a Full Sea
Chang-Rae Lee

Train Dreams: A Novella
Denis Johnson


How We Got to Now: Six Innovations That Made the Modern World
Steven Johnson

The Sixth Extinction: An Unnatural History
Elizabeth Kolbert

Creative Confidence: Unleashing the Creative Potential (unfinished)
Tom Kelley

Factory Man: How One Furniture Maker Battled Offshoring, Stayed Local – and Helped Save an American Town
Beth Macy

Maphead: Charting the Wide, Weird World of Geography Wonks
Ken Jennings


Notable Articles

The Case For Reparations –  Ta-Nehisi Coates
Reza Aslan on What the New Atheists Get Wrong About Islam
How Fossilized Ideas Live on Even in Science – Andrew Crumey
How To Get Beyond The Parasite Economy – Eric Garland
Silicon Valley’s Youth Problem – Yiren Lu
The Mammoth Cometh
The Collateral Damage of a Teenager


How Bad Products Get Made

This article recounts how the Pontiac Aztec, perhaps the most notable automotive failure in recent history, came to be. I suggest reading the whole thing as a lesson in how bad products get made. A few things stood out as significant to me:

Targets and goals that aren’t grounded in actual user needs:

“Wagoner and the automotive strategy board decreed that henceforth, 40 percent of all new GM products would be “innovative.” That started a trend toward setting internal goals that meant nothing to the customer.”

I’ve emphasized that a clear vision and support from upper management is an absolute necessity, but leading by dictate is often disastrous:

We’ve all made up our minds that the Aztek is gonna be a winner. It’s gonna astound the world. I don’t want any negative comments about this vehicle. None. Anybody who has bad opinions about it, I want them off the team.

Adhering to first principles you’ve established with customer input is critical. And the manifestation of those – the design – is something that’s arrived at through a process of invention:

Many people in the car business do not understand that a vehicle has an image. To them, a vehicle is a collection of attributes. If your attributes are better than the other guy’s attributes, you’re gonna win. It’s engineer thinking, along totally rational lines.

Does Apple Hate Old People?

Recently, Apple tripped me up trying to install software from the App Store on a new Mac. It had been a while since I’d done this, so the security questions were pretty obscure: “What was model of your least favorite car?” and somewhat less so, “What was the model of your first car?”. After quite a few tries, I was kicked out and had to set up a phone call with Apple support (answering security questions in my open-plan office). Once I was let back in to my account, I was prompted to establish new security questions. This is what I was offered:
Possible security questions Apple offers users
The intent of this is find answers that only the account holder knows and may not exist online. Most people don’t realize you can put whatever value you want as an answer, but it might be self-defeating to ignore the prompts and forget what you entered. For someone getting on with his life, and probably more than halfway through it, these seemed like a stretch for me:
9 questions (half the total) that involve “first” memories.
3 questions from early childhood, depending on how you count.
3 or more questions questions from high school.
Perhaps the team in charge of this is very young (as tech companies can be) and these memories are not so distant, or there’s an intent that I’m not appreciating. I hope there are culturally-specific versions of this, since not every country has a population that relies on automobiles or has an educational structure like the US does.
Or maybe I really am just losing it.

The Rental Car Test

I recently spent nearly two weeks using a rental car – a 2013 Ford Explorer – on a family vacation. We drove from New York to Chicago, around Chicagoland and Northern Illinois, and then back to New York, with daily trips in the car. One of the highlights was taking advantage of the My Touch infotainment system in the vehicle. My car at home is a decade-plus old Subaru, so “hi-tech” for me means a cassette deck. Call it a busman’s holiday, but I was excited to use an up-to-date interactive system that’s in so many vehicles (and is somewhat notorious).

My first and lasting impression is that the UI is more suited to a tablet than an automobile. The screen was reasonably responsive, and there was some pairing with physical (albeit digitized) controls. Giving Ford the benefit of the doubt, I’m sure they tested it in a moving vehicle, but I found the the typography too fine, the layout cramped, and enough nomenclature and flow quirks to trip me up to the point of defeat. I couldn’t escape the feeling that this worked well in a simulator and on someone’s tablet, but hurtling at 70MPH down the highway is an entirely different experience.

It seems to me that a serious usability test for vehicle manufacturers building these systems is how quickly a car rental customer could figure out basic tasks. Like climate control, the stereo, and then synching a mobile phone, getting directions, and on to more complex tasks. Like a lot of rental car drivers, I get into a car in the airport parking lot and drive off without stopping for couple of minutes to figure out controls beyond the mirrors and seat. Frequent rental car customers might actually have an advantage, since they could be exposed to a multitude of systems, but I don’t know how much thought people give to how things work. Perhaps a “simple mode” for frequently-accessed items, and — this is a minor annoyance — some way of resetting everything so that a new renter doesn’t have to encounter a previous user’s radio stations, trips, etc.

Not nearly as ubiquitous as the airticket redesign projects (1, 2, 3, 4, etc.), but perhaps much more meaningful in potentially saving lives — and as a design exercise, significantly more challenging — is the vehicle touch screen redesign exercise. This one caught my eye as being one of the better ones of the breed: it showed an appreciation for the context by attempting to use multi-touch to overcome the lack of physical affordances in a screen; another one addresses Tesla’s attempt to overcome the problem (by going all-in with a giant screen and no physical controls) with an attempt at splitting input and output into two different screens. Actually, the Ford Explorer I rented had some elements of this, although it seemed they were unable to restrain themselves. In the end, I don’t think a heavy reliance on a touchscreen is a good idea – reserve them for what computers do best: complex, nested, changing features, and use physical controls (with digital refinements) for the top 3-5 user needs.

News reports tell me that Apple and Google/Android are getting into the car UI business, which may be welcome news. Its difficult to say if touchscreen GUIs are too far outside the expertise of carmakers to do well, or its an issue of large companies not being able to do small things well. While an outsider perspective might work well, the decades of deep expertise carmakers have is extremely valuable and can’t be discounted.

What I Read in 2013

I don’t think I read quite as many books in 2013 as I did in 2012, but I’m pretty sure I read substantially more long-form and short-form content. I’m on a better pace so far this year, but I’ve noticed that I tend to read much more in the winter and during my summer break. Here, in no particular order is what I managed to get through.

The Orphan Masters Son – I can’t recommend this enough.

The Teleportation Accident – I was entertained, but not completely thrilled with this.

The Testament of Jessie Lamb – Well crafted, if not completely satisfying scifi.

Transatlantic – Fairly sprawling, beautifully written historical novel.

The Windup Girl – I actually enjoyed this a lot more than I thought: another scifi book with a good mix of tech, plot and character development.

The Plot Against America – An alternate history that was very entertaining and well-written.

People Who Eat Darkness: The True Story of a Young Woman Who Vanished from the Streets of Tokyo–and the Evil That Swallowed Her Up - Reporting of a murder that reads like fiction.

1493: Uncovering the New World Columbus Created – Deeply interesting to me, and certainly sends a message about how we continue to ravage this planet.

A Constellation of Vital Phenomenon – Really stunning piece of fiction.

The Brothers – If you’ve ever wondered why the rest of the world hates the US, read this.

Notable Articles

Why it’s time to lay the selfish gene to rest – David Dobbs – Aeon and the Gulf Between Planning and Reality - Clay Shirky

And Then Steve Said, ‘Let There Be an iPhone’ – Fred Vogelstein

American Schools Are Failing Nonconformist Kids. Here’s How. – Elizabeth Weil

What Paintbrush Makers Know About How to Beat China – Adam Davidson

Linda Stone on Maintaining Focus in a Maddeningly Distractive World – James Fallows

The Enlightenment’s ‘Race’ Problem, and Ours – Justin E. H. Smith

Why Can Some Kids Handle Pressure While Others Fall Apart? – Po Bronson and Ashley Merryman

The Innocent Man, Part Two: Texas Monthly December 2012 – Pamela Colloff

Designers, not Dribbblers

Paul Adams has written a fantastic short article (I suppose it might even be considered long-form these days, but that’s another topic) about what he calls The Dribblisation of Design. In it, he derides the growing trend, as he identifies it, of designers posting attractive mockups and reworks of existing or fictitious products on Dribbble, a gallery of member’s work, in the absence of any context. By context, he means the business environment that almost all substantial product work takes place in. He’s not knocking the desire of designers to show off their work, but the undue influence that showing work out of context can have.

Dribbble itself shapes the conversation to some extent, the medium shaping the message, with highlighting of colour palettes and other superficial details prominent in the UI. People look and people emulate.

Designers can easily retreat into pushing pixels because “it’s just more fun to draw nice pictures and bury oneself in pixels than deal with complicated business decisions and people with different opinions.”

Regrettably, this is a problem that has always existed and will never go away. Designers come from all sorts of backgrounds, with a huge array of skills and experiences informing their practice. Richard Buchanan, one of my professors at CMU talked about design practiced across four orders, and while he emphasized that these should not be considered as existing on a continuum or as outcomes, it is a useful framework for understanding the breadth and depth of what a contemporary product designer should be addressing:



Strategic Planning

Systemic Integration


Signs, symbols, and images





Physical Objects




Activities, services, and processes



Systems, environments, ideas and values

Most designers aren’t trained to do more than decorate – to spend time in the upper left, where their skills are most easily displayed and recognized. The woeful lack of preparation designers are getting in most schools is a serious issue. I think Paul is addressing an elite group of product designers in this piece, not the vast majority of designer/decorators.
Not mentioned in Paul’s piece are the structural issues within most contemporary product development environments that favor the atomization of output, further exacerbating a designers worst habits. He does talk about the need to align work to company vision and provides some excellent guideance on how to frame that understanding. Processes that disallow for a holistic view of the business problems and user goals are only going to yield fragmented, disconnected experiences. They might look great, but they won’t be solving the real big problems designers should be.