If you enjoyed the inaugural episode of “Wireframe”, you’ll love this second installment, just released today. The title is “Good Desgn Is Good Civics,“ and it looks at how the city of Boston tried to package its municipal government into app form, and what it learned along the way about how design serves its people. You can listen to it above but be sure to subscribe so you don’t miss an episode.
If you’re not familiar with “Wireframe,” it’s a unique kind of design podcast, hosted by yours truly. Instead of merely interviewing well known designers, we dig into the world of interaction design via deeply researched reporting and engaging narratives. In other words, the focus is on stories instead of résumés. You can read more in this blog post.
This morning, during the keynote address for Adobe’s MAX 2018 conference, I demoed the latest enhancements to our Adobe XD design tool for UX/UI designers. One of these enhancements is something that I’m particularly excited about—and also personally proud of. That’s the new ability to design, prototype and share with voice as a medium.
Let’s say you’re designing a product that has a voice search feature built into it, perhaps something similar to Spotify’s mobile app. Now, in addition to being able to design and prototype the visual layout, you can also define the actual voice inputs and outputs for that assistant. That means you can just type in the exact phrase that you want the app to listen for—XD will actually listen for you to utter the text that you enter and, when it hears it, will advance the prototype. And it also means that you can type in the actual responses you want to hear back from the app—this latest version of XD includes the powerful Amazon Polly text-to-speech service right in the app. It’s ridiculously easy to build these voice interactions; the video below demonstrates this in action.
The upshot is that Adobe XD is now the only design tool that allows you to create realistic voice prototypes that emulate any voice-activated system or voice assistant. Even better, because this is integrated into XD alongside the app’s more “traditional” design tools, it becomes incredibly easy to revise and refine your voice designs very, very quickly. That ability to iterate has been the missing link in voice as a medium. Even as Amazon Alexa, Google Assistant, Siri and other voice assistants have taken off like wildfire, designers working in voice have been stymied by the nearly complete lack of voice tools oriented around the design process. All that changes today.
The launch of these voice features is especially satisfying for me for two reasons. First, I’m a big believer in the idea that voice is well on its way to becoming an integral part of experience design. This just seems like a foregone conclusion to me. Smart speaker growth is already torrid, and voice assistants are becoming a natural way for a new generation of users to interact with technology. What’s really exciting about this is that voice as a medium is still so young. There are lots of challenges still to be resolved with voice, and it’s designers who are best suited to forge these new solutions.
I’m especially proud of voice in XD because I was able to play a role in making this all happen. Early in 2017, I was introduced to Mark Webster, who was then the founder and CEO of Sayspring, a startup building a design-oriented voice prototyping tool. As soon as Mark demonstrated Sayspring to me, a light bulb went off in my head—I recognized immediately that what he and his team were building was something every designer should have in his or her toolbox.
Readers of this blog may remember that later that year I published an extensive interview with Mark about the challenges of designing for voice. That interview was my way of evangelizing the importance of a design-oriented approach to voice. This was intended for the design community at large, but it was also not so subtly intended for an audience within the halls of Adobe as well. I started lobbying my colleagues to consider voice as a new medium that Adobe XD should address, and pointed to the interview as a kind of primer on the concept.
Then, in October of last year, Mark joined us at Adobe’s MAX 2017 conference in Las Vegas, where we found time for him to sit down for a private meeting with Paul Gubbay, Adobe’s vice-president for design and web products, Andrew Shorten, senior director of product management for Adobe XD, and me. Mark demoed Sayspring, showed us how to build a voice prototype in minutes, spoke commands to an Echo device and we heard it respond. Immediately Paul and Andrew saw the potential that I had seen. That kicked off a series of discussions that eventually led to Adobe acquiring Sayspring in April of this year. Mark and his team then moved into Adobe’s New York offices (not far from my desk, actually), rolled up their sleeves and began working like mad to build the voice features shipping in today’s release.
This whole journey has made for one of the most interesting years of my career. Working on Adobe XD was already an invigorating challenge, but to get to play a small role in bringing a whole new kind of design and prototyping to millions of designers, that has been truly amazing. For me, it all reflects the rich possibilities that exist at Adobe. Not just the ability to move at scale and to make strategically unique acquisitions like we did with Sayspring, but also the willingness to look ahead and anticipate changes in the very nature of design. Voice was already one of those transformative technologies on a path to wide acceptance, but it’s also very much one of these media that will be catalyzed in wholly new ways with the participation of designers. I can’t wait to see what happens next.
Today marks the debut of “Wireframe,” a podcast about user experience design brought to you by Adobe and Gimlet Creative—the host is yours truly. You can listen to the first episode embedded above, but be sure to subscribe to the podcast so you don’t miss each week’s new episodes.
There are a ton of podcasts about design out there, but almost every one of them follows a standard interview format: the host welcomes a famous designer, asks him or her about how they got their start, goes over their background, their job, their challenges etc. Some of these podcasts are terrific; I’ve been lucky enough to have been interviewed by some wonderful hosts on shows just like that.
“Wireframe” is different though. Its format is the kind of high-quality, deeply researched storytelling you might be more familiar with from public radio, or shows like “This American Life.” There are interviews, of course, but instead of a single interview subject, each episode might feature snippets from interviews with as many as four or five different people. What brings these voices together is the theme for each episode. In the first episode out today, the theme is the role that user experience design has played in some near-disasters in American history, and how that has influenced the way we all think about design and technology. Future episodes will cover design’s role in city services, the origins and impact of emoji, the controversy of addictive design, and more. In short, this show is about stories, not résumés.
The ambition here is twofold. First, we wanted to elevate the discussion around design so that it’s treated with the same seriousness, thoughtfulness and sense of fun as any general interest subject matter—arts, culture, technology, sports etc. It’s surprisingly uncommon to hear or read about design in this manner, as we’re much more accustomed to how-to tutorials or inside-baseball articles. It’s much rarer to find stories about design that are exhaustively researched and fact-checked, that are produced to professional broadcasting standards, and that take a “big picture” view of the impact of our craft. And it’s no wonder why; each episode of “Wireframe” took dozens of hours of research, writing, recording, editing and production.
The second goal here is to talk about design in a straightforward, engaging way that draws in not just seasoned designers but also a wider audience of people who are curious about our craft. Put another way, we wanted to show how design is relevant to the world at large.
That’s why we partnered with Gimlet, a company with a fantastic track record for creating hugely popular general interest podcasts. They brought an invaluable journalistic sensibility that focused the whole effort on telling stories in clear, compelling language that anyone, regardless of their level of design expertise, can listen to and actually enjoy. It’s a fine line to walk between conveying the myriad of complex ideas behind design and portraying its wide reach in plain, accessible terms. But in my view it was exactly the right challenge. As I’ve said in the past, the more lucidly design can explain itself to the general population, the more the world will value its benefits.
This podcast has been a true passion project for me over the past several months. More goes into each episode of a show like this than I ever had any idea, and it was so humbling—and fun—to learn a bit of it from the folks at Gimlet. I honestly think you’ll get a kick out of it. Please give it a listen, subscribe in Apple Podcasts or wherever you get your podcasts, and let me know what you think.
The massive disruption that ride-hailing apps like Uber and Lyft have visited on the taxi industry stirs up so many conflicting feelings for me. I use these services all the time but the larger impact of my patronage has been weighing on my conscience more and more lately. Not least because, from a certain perspective, it’s clear that design lays at the heart of both the genuine innovation and the disturbing dissonance of this transformation in transportation.
It’s no secret that Uber and Lyft, in order to justify their exorbitant market valuations, are barreling towards a future in which the way we move about cities is reinvented by autonomous vehicles. It’s at that point that they’ll be able to do away with the pesky expense of human drivers. And it’s also at that point that the companies will have decisively made the shift to true technological innovation.
Until that yet-to-be-determined date, the frank truth is that what propels these companies forward is not really technology innovation so much as design.
Of course, the ability to hail a car on your phone and then have your request instantly dispatched to a driver in your vicinity is an impressive technological feat. But the actual ride, the core of the value, is still technologically unchanged—you’re still being driven in a combustion engine vehicle by a human. (Even if your driver picks you up in a hybrid or electric car, that technology wasn’t brought to you by the app or these companies.)
The real innovation that Uber and Lyft have brought to bear is in the transformation of the user experience of your ride: the ability to gauge your driver’s distance from you; the presentment of the driver’s name and the make and model of his or her car; the option to follow along with the route to your destination; and then the prompt to rate and review your ride at the end. These are the kinds of things that make an Uber or Lyft ride fundamentally different from stepping off the curb and waving down a taxi. They rely on technology, of course, but really they amount to “designing the ride,” or the application of user-centric thinking to enhance the experience of being driven across town.
Uber vs. Lyft and Beatles vs. Stones
In a way ride hailing as a technology was commoditized almost as soon as it was birthed into the world. You can see this in how the basic functionality of both Uber and Lyft’s apps have largely stayed the same over the years while the design and branding approach of both apps has been updated and enhanced with great frequency. This doubtless reflects a recognition on the part of both companies that their technology is virtually indistinguishable from one another, at least to consumers. When a business finds itself in a position like that, one of the best ways to compete is with design.
All of this has yielded a kind of user experience boon to ride hailing customers. The apps seem to be continually, breathlessly one-upping each other with new interface features and slicker interactions, and they’re overhauled periodically with ambitious and sometimes dramatic redesigns. Put simply: the design of these apps is getting better all the time. It’s one of the closest equivalents to a Beatles/Stones rivalry that we’ve ever had in interaction design, and it’s been exciting to watch.
In the short history of our craft, you would think this could be regarded as an unalloyed success for the profession, and certainly as a triumph over the legacy taxi industry’s stodgy resistance to design. Before Lyft and Uber taxi and limousines had operated virtually unchanged for decades. (It was a big deal in the early 2000s when you could start using a credit card in New York City cabs, a laughingly incremental innovation.) And the experience of being driven by a hack was often erratic and inconvenient, to put it mildly. I recall ruefully the annoyance of trying to hail a taxi on busy weekend nights while at least three or four other people were doing the exact same thing on the same street corner. That’s when they’re available; hailing a cab in inclement weather has always been one of life’s least noble chores. And of course taxis and limousines have, at best, spotty reputations for picking up passengers of color, or for being available or timely in low income neighborhoods.
It’s almost as if, once we added design to the equation, everything got better. All of a sudden you could reliably get a ride on any street corner, at any time, almost without regard for how many other customers are competing for rides of their own. Rides are cheaper now, too, both because each Uber and Lyft transaction is essentially underwritten by investment capital and because you can know the cost before you even hail that ride. Taxi drivers can no longer “show you the park,” as they used to say when they took unsuspecting out-of-towners the long way round to their destinations.
All these improvements were made possible by design, and they’ve made a difference—a huge one. There would be no “unicorn” valuation for Uber or Lyft if they hadn’t employed designers to fundamentally improve the taxi experience.
But of course, this isn’t the whole story, not by a longshot. The lightning speed with which ride hailing apps have captivated consumers has also brought some substantially troubling unintended consequences.
To compound that problem, there is no path forward from driving into ownership. Cab drivers in many cities can eventually become licensees or medallion owners, building equity in their professions. In the past this has been a reliable trajectory for many immigrants who have been able to start as taxi drivers and become owners of small fleets of cabs, propelling them into middle class life. With the advent of Uber and Lyft, the value of medallions in New York City, for example, has fallen off a cliff, effectively wiping out the financial futures of countless drivers.
Whether you look at this disruption as either an unfair attack on a working class profession or as a basic and perhaps inevitable outcome of free market evolution, it’s much harder to dismiss the effect that Uber and Lyft are having on our physical world.
Where they once promised to lessen traffic, it’s now become clear that these services instead increase congestion—precipitiously. In a study of nine major metropolitan cities in the United States—Boston, Chicago, Los Angeles, Miami, New York, Philadelphia, San Francisco, Seattle and Washington—researchers estimate that ridership is adding as much as 5.7 billion miles of driving per year to streets.
This likely stems from the fact that customers aren’t hailing Uber and Lyft instead of driving their own cars. In fact, that same study suggests that at least half of the rides hailed on these services would not have been taken by car at all; they are journeys that customers would have taken by foot, bike or public transport, or perhaps even not at all. The gas consumption—and attendant pollution and environmental damage—required to support all of this additional driving is staggering. But think also about all of the fossil fuels that are required just to allow Uber and Lyft drivers to continually circulate around a city so that that there will always be one near you when you need it.
You Can Never Go Back (to Taxis)
Earlier I contended that very little of the innovative value of these services could’ve happened without design. Well here is the other side of that coin: At some point the total civic benefit of these services begins to look less like a misguided convenience and more like a lavish extravagance that none of us can afford. And the rapidity of design’s success here, combined with how lasting it’s likely to be makes this look more and more like a design-led calamity.
Uber and Lyft rose to prominence so quickly—in roughly just a half decade—but it seems unlikely that a solution to this predicament will happen nearly so quickly. As American society has proven again and again, it is unwilling to use roads less, only more. The habits that we’ve all formed so quickly around on-call, near instant ride-hailing are going to be incredibly difficult to reverse.
It’s not an option to just go back to the way taxis and limousines operated a decade ago. That legacy industry is not just in an economic shambles today, but it remains as problematic as ever. Even as it functioned as a gateway to the middle class for countless drivers, it’s been historically rife with transgressions and corruption. If anything, the design innovation in Uber and Lyft only served to highlight how generally unfit for the public the whole industry has long been.
Furthermore, even if there were some kind of a public campaigned waged to return to traditional cabs (and it would have to be an incredibly successful one to make an impact), the bell of ‘good design’ can’t be unrung. We’ve now seen how design can remake the experience of a cab and there’s no going back.
One of the most powerful aspects of the Uber and Lyft approach is the dual rating system for drivers and passengers. It’s been remarkable to me how it’s influenced my conduct as a passenger; I’m much less prone to being rude or even giving negative feedback directly to drivers knowing that they’ll be rating me as well.
But when I get into a taxi cab, not only do I find that I’m less personable with taxi drivers, but I also find that the reverse is true, too. In the past year, I’ve taken rides with yellow cab drivers who conduct private conversations on their phones and ignore me entirely; who disregard my requests to take certain roads to my destination; who cite their need to make short return deadlines as reasons why they can’t add stops to a trip; who are flagrantly untruthful about fare estimates; and who are just plain rude. If you have reservations about Uber and Lyft, the user experience of yellow cabs are not a compelling alternative.
Disruption vs. Design
Any sober assessment of this situation would likely conclude that there are elements of both traditional taxi service and ride hailing apps that are desirable. On the one hand, we want taxi driving to be a sustainable profession, with hack licenses and medallions distributed in reasonable quantities so as to mitigate congestion. On the other hand, we also want a good experience for our rides, we want technological innovations, and we want a mutually respectful relationship between rider and passenger. Right now the prospects for achieving that balance seem very remote.
The widely dissatisfactory nature of this current situation suggests to me that design as a force for “disruption” is deeply problematic. If you look at this mess we’re in, it’s pretty clear that all that we’ve done here is disrupt the status quo. While there is merit to that, as a profession we’ve allowed ourselves to be swept up too easily by the enormous emphasis (read: economic value) that the tech industry has placed on the concept of disruption.
It’s reasonable to look at the Uber and Lyft experiment as an attempt to redesign everything about taxis. In some ways the attempt has been unexpectedly successful—if you had told me a decade ago that this market would become one of the most consequential proving grounds for design ideas ever, there would have been no way I’d have believed you. But that’s what it’s become.
Design has disrupted taxis in a massive, almost unprecedented way. But good design doesn’t merely aim to disrupt—it should set out to actually build viable solutions. Designers shouldn’t look at a problem and say, “What we’re going to do is just fuck it up and see what happens.” That’s a dereliction of duty.
But in a very real sense, that’s just what design has done with this challenge of how people get driven across town. Design has focused on the details: on the challenge of getting the interface just right; on “optimizing the funnel” for new and lapsed customers; on fine-tuning the choreography between app notifications, driver interactions and payment; and on outfoxing the competition. Meanwhile, the bigger picture has gone largely ignored.
It’s difficult to write a post like this without implying bad behavior on the part of the teams, past or present, who work on these products. That’s not my intention.
There’s a tough discussion to be had here about responsibility. That includes the question of “To what extent should the Uber and Lyft design teams, past and present, be held accountable for the creation of this inescapable new challenge of modern life?” But we should also ask, “To what extent should the entire design industry be held responsible for peddling our relentlessly sunny prognostications of how design can improve the human condition, all without regard for deeper discussions as to the meaning and impact of our work?”
If anything, this situation reflects poorly on the entire design industry—and on our inability to connect our work with the larger context of what we put into the world. I’ve argued before that as a profession we’re inexperienced at this level of discussion and thoughtfulness. There is a long road ahead to being able to incorporate this kind of awareness into our work methods in a way that’s productive and complementary, rather than at odds, with the companies that employ us.
By the same token, that hardly absolves design in the present. The teams at Uber and Lyft have a responsibility to engage in a dialogue, privately and publicly, about the impact of their work. And we all have a responsibility to ask questions about that very same subject, to hold all of us, together as an industry, responsible for the outcomes of our craft. We can’t think of ourselves merely as disrupters. When we take on a challenge, when we endeavor to apply our tools and thinking and labor to problems, we have to commit ourselves to producing complete, viable and sustainable solutions. We have to finish the whole job.
I try to post these roundups as soon as I can after each month closes but I’m barely getting this one in before October. And it does seem like a long time ago that I saw Spike Lee’s “BlacKkKlansman” at the theater, but the disappointment still lingers.
It’s not wise to walk into any of this director’s movies expecting perfection, but I’ve come to expect, at least, a kind of thrilling audacity, a go-for-broke sensibility that bends narrative and polemic together in unexpected ways. That’s what Lee’s 2015 film “Chi-Raq” was like: not altogether successful, but still wildly ambitious, and pretty amazing to watch.
By contrast, “BlacKkKlansman” is almost shockingly…conventional. Its crazy premise—an African-American cop fools the Ku Klux Klan into accepting him as one of their own—never reveals itself to be anything crazier than the way it’s described—no new layers are peeled back, no unexpected twists are presented. It’s just kind of boring, actually. And by the end, when Lee hastily motors through various plot resolutions and tries to tie the movie’s historical milieu into present day events, the total effect feels slapdash. A missed opportunity.
Here are all fifteen movies I watched way back in August.
There are literally hundreds of designers working at Adobe in offices all over the world. Back in July we got all of them together for four days of lectures, workshops and discussions from both Adobe staff and guest speakers from outside the company. We called it Design Summit; a huge internal design conference held in San Francisco’s massive Pier 35 event space.
One of the most popular sessions was this talk from Zimbabwean designer Farai Madzima, who joined us for the second day of our conference, flying in from Ottawa where he works as a design leader at Shopify. In a truly not-to-be-missed lecture, Madzima floored the audience with his thoughts and experiences on cultural bias in design. If you only watch one video today, make sure this is it:
Design Summit was, for me, a thrilling reminder of Adobe’s commitment to the craft and the industry: We paused projects all over the company for a week; spent a small fortune flying designers in from every corner of the globe; held a special invitation-only event for the Bay Area design community; and discussed process, creativity, accessibility, diversity, inclusion, technology, ethics, the future of the craft, and more—truly a range and depth of design discussion that few if any companies would ever entertain.
On top of it all, it’s worth noting that the event was also visually stunning, thanks to the stellar work of the Adobe Design Brand Team. They created this beautiful identity system from whole cloth, all inside of just a few months and alongside their regular workload. They then implemented it in just a few days as environmental graphics throughout Pier 35, as smart looking swag and paraphernilia distributed to every attendee, as video interstitials on stage—and even in the form of pop-up shop inside the event space. Amazing work; you can see more if it in this Behance project.
Libraries are being disparaged and neglected at precisely the moment when they are most valued and necessary. Why the disconnect? In part it’s because the founding principle of the public library — that all people deserve free, open access to our shared culture and heritage — is out of sync with the market logic that dominates our world. But it’s also because so few influential people understand the expansive role that libraries play in modern communities.
When I started working professionally and earning a paycheck I got in the habit of buying the books I wanted to read and basically stopped going to libraries of any kind altogether. That lasted until just a few years ago when my daughter learned to read and became an avid bookworm. Now it’s unusual if we go more than a few weeks without visiting one or more branches of the Brooklyn Public Library system.
We’re lucky that the library system in Brooklyn is relatively well funded. You can reserve, borrow and renew books via the system’s web site. You can also do the same with e-books using the reasonably good if imperfect Libby app from Overdrive (I’m in the middle of a Lee Child book on my phone right now thanks to this). Pretty 21st Century, right?
A Brooklyn Public Library card in and of itself is kind of a remarkable thing too. To begin with, the current design sports an illustration from Maurice Sendak’s immortal “Where the Wild Things Are,” making it easily the most aesthetically sophisticated card in your wallet. That card also lets you access the free Kanopy streaming movie service which has some great classic as well newer independent films—basically it’s like Netflix, but you don’t have to pay for it and the content is actually good. And finally the card also gets you free access to thirty-three New York City museums.
All of that is a remarkable deal, but what has struck me most about coming back to public libraries is how so many people get so many different uses out of the buildings themselves. As a public space, they’re unlike any other. As Klinenberg writes:
Libraries are an example of what I call ‘social infrastructure’: the physical spaces and organizations that shape the way people interact. Libraries don’t just provide free access to books and other cultural materials, they also offer things like companionship for older adults, de facto child care for busy parents, language instruction for immigrants and welcoming public spaces for the poor, the homeless and young people…
I recently spent a year doing ethnographic research in libraries in New York City. Again and again, I was reminded how essential libraries are, not only for a neighborhood’s vitality but also for helping to address all manner of personal problems.
For older people, especially widows, widowers and those who live alone, libraries are places for culture and company, through book clubs, movie nights, sewing circles and classes in art, current events and computing. For many, the library is the main place they interact with people from other generations.
For children and teenagers, libraries help instill an ethic of responsibility, to themselves and to their neighbors, by teaching them what it means to borrow and take care of something public, and to return it so others can have it too. For new parents, grandparents and caretakers who feel overwhelmed when watching an infant or a toddler by themselves, libraries are a godsend.
In many neighborhoods, particularly those where young people aren’t hyper-scheduled in formal after-school programs, libraries are highly popular among adolescents and teenagers who want to spend time with other people their age. One reason is that they’re open, accessible and free. Another is that the library staff members welcome them; in many branches, they even assign areas for teenagers to be with one another.
I’ve seen for myself real life examples of virtually all of these use cases. It really opened my eyes to how vital a civic institution the libraries in my community are. But I take mild exception to the emphasis that Klinenberg places on a library’s ability to “address all manner of personal problems.” That phrasing gives the impression that a library is a place you go principally to solve some kind of challenge.
While that’s often true, it’s also true that a library is a building that’s uniquely open to any purpose you bring to it. Your business there could be educational, professional, personal or even undecided, and you don’t need to declare it to anyone—you can literally loiter in your local public library with no fear of consequences.
Even more radically, your time at the library comes with absolutely no expectation that you buy anything. Or even that you transact at all. And there’s certainly no implication that your data or your rights are being surrendered in return for the services you partake in.
This rare openness and neutrality imbues libraries with a distinct sense of community, of us, of everyone having come together to fund and build and participate in this collective sharing of knowledge and space. All of that seems exceedingly rare in this increasingly commercial, exposed world of ours. In a way it’s quite amazing that the concept continues to persist at all.
And when we look at it this way, as a startlingly, almost defiantly civilized institution, it seems even more urgent that we make sure it not only continues to survive, but that it should also thrive, too. If not for us, then for future generations who will no doubt one day wonder why we gave up so much of our personal rights and communal pleasures in exchange for digital likes and upturned thumbs. For years I took the existence of libraries for granted and operated under the assumption that they were there for others. Now I realize that they’re there for everybody.
In spite of all the high-minded cinema fare I profess to care for so deeply, the movies I get most excited about are usually popcorn action thrillers. That explains why, if I’m honest, “Mission: Impossible—Fallout” was probably the movie I’ve looked most forward to all year. Its predecessor, “Mission: Impossible—Rogue Nation” pulled off the unthinkable feat of being both the fifth and most interesting installment in an already excellent franchise. When I learned that its director, Christopher McQuarrie—one of the best filmmakers working today—would return and that “Fallout” would be a direct sequel, I started getting very, very excited.
For my money, this is a series that has only gotten better with each new installment. No one asked me to rank them from least to most favorite, but I will now anyway, as the ordering is actually quite elegant: I, II, III, IV (“Ghost Protocol”), and then V (“Rogue Nation”). In fact, I re-watched them all in July in anticipation of “Fallout” which, as it turns out, completes the progression by being the best one yet. We’re all well aware by now of star Tom Cruise’s almost disturbing obsession with risking his own life for our entertainment, but in this outing he and McQuarrie achieve an almost sublime synthesis of character development and action. What’s communicated through stunts, body blows and explosions here is as meaningful as what’s expressed through dialogue. It’s as close as a large-scale Hollywood action has ever come to an auteurist psychological drama.
One of the unintended consequences of having banked a string of six highly successful, generally well-reviewed films in a row is that the series has also created an unmistakable snapshot of popular contemporary thinking. Beyond the cracking good action, after watching the complete series it became clear to me that at heart these movies are about the tension between physicality and technology.
This has been true from the start. The very first installment also happened to produce the series’ most lasting image: that of Tom Cruise dangling from wires as he attempts to extract data from a highly secure computer terminal. Since then, a similar act of extraction has figured intrinsically into the plot of all of these films. Over and over again they posit that human movement and physical action is the only reliable way to render some crucial value required by people from the intractable grip of technology, whether what must be breached is a data center at a CIA compound, a nonsensically located server room on a forbiddingly high floor of the Burj Khalifa, or any number of situations made fraught by technology’s uncannily accurate ability to subvert the truth (read: the countless masks that are a hallmark of the franchise).
It’s also no accident that Tom Cruise is commonly referred to as today’s “last movie star.” As a conceptual whole, “Mission: Impossible” tries to make sense of how a classic, cinematic idea of masculinity can overcome technology’s encumbrances. Sure, Cruise’s Ethan Hunt character is always abetted by his technologically incisive colleagues Luther Stickell (Ving Rhames) and Benji Dunn (Simon Pegg), but these are strictly secondary characters—comic relief, even. Ultimately the resolution of the plot falls to the alpha male, Cruise himself. This series is a reflection of society’s struggle to reconcile heroism and hacking.
And that’s all I have to say about “Mission: Impossible” for now—unless you want to subscribe to my newsletter, where I’ll have some more totally unnecessary thoughts for subscribers only. Meanwhile, here is the full list of all fifteen movies I watched last month, only seven of which starred Tom Cruise!
To our own detriment, designers prefer to think about “how” much more than “why.” This was demonstrated in my blog post from earlier this week but here’s another good example—or perhaps it would be more appropriate to call it a bad example. You may or may not find it disturbing.
Last month the widely respected, “evidence-based user experience research, training, and consulting” firm Nielsen Norman Group published a fascinating report on best practices to consider when designing websites for children. Its author, Feifei Liu, summarizes a study that the firm did in which they interviewed kids aged three to twelve to learn how they behaved performing a series of interactive tasks. Liu writes:
Our research with kids on the web and mobile devices shows that the physical development of motor skills and motor coordination influences children’s ability to interact with devices.
Roughly, children under five have limited motor abilities and require very simple physical interactions on touchscreens. For kids between six and eight years old, their developing motor skills allow them to perform simple interaction gestures on laptops like clicking and simple keyboard usage. Whereas starting around the age of nine years, more advanced interaction techniques become possible. Around the age of eleven years, children become able to use the same range of physical interactions as adult users. (Though obviously, their mental development stage and educational level still dictate simpler overall user interfaces for eleven-year olds than for adults.)
That’s the executive summary, leading off the top of the report. The rest of it digs into those findings, detailing a series of recommendations for designers creating websites for kids. Some of these include: emphasizing swiping, tapping, and dragging on touchscreens; avoiding interactions that require dragging, scrolling, and clicking small objects; and generally accommodating the limited motor-coordination facility of this audience.
Useful stuff. I don’t dispute the findings at all. But it’s disturbing that the report focuses exclusively on usability recommendations, on the executional aspect of creating digital products for kids. There’s not a single line, much less a section, that cares to examine how design impacts the well-being of children.
This seems particularly egregious when one considers current societal discussions about how digital technology impacts younger users. Recent studies point out that mobile device usage among young children has skyrocketed to an average of as much as two hours per day, up from as little as just five minutes a day at the beginning of this decade. Meanwhile, the American Academy of Pediatrics revised their recommendations for device usage amongst children this year to just one hour per day, arguing that “Too much media use can mean that children don’t have enough time during the day to play, study, talk, or sleep.” The non-profit group Common Sense Media found that, contrary to advice from pediatricians, much of this time spent in front of screens is happening just before bedtime, and children in lower-income families are much more likely to spend more time on devices than those from more affluent families. And a lot of attention has been paid to San Diego State University professor of psychology Jean M. Twenge’s studies of the first generation of teenagers to grow up with mobile technology, and the radical and often worrying shifts in behavior that smartphones have engendered in them.
In fairness, none of this is incontrovertible proof that screen usage is harmful to children, but it’s also safe to say that there’s reasonable cause for concern. At the very least thoughtfulness is warranted in the design of digital products for this audience.
It’s also worth noting that Nielsen Norman Group is famously focused on the narrow subject of how to make digital experiences as usable as possible; their expertise on usability is widely recognized and rightfully acclaimed. The larger question of whether a design solution is in the best interests of its users has always been purposefully beyond their scope. But pretending that there is no link between the usability of an experience and the long-term well-being of its users is, frankly, a specious position at best. Particularly for this target group of users.
Habits are formed around the usability of a product; if an app or website makes it easy to complete a task, users are likely to do it more often than not. Usability advocates often treat this as an inherently good quality; by and large every business wants their products to be easier rather than more difficult to use. But as the aforementioned research suggests, it’s become clear that guilelessly encouraging longer, more frequent sessions isn’t necessarily better for kids.
I would contend that it’s really no longer useful—or responsible—to think of the work we as designers do in such narrow terms. You don’t even need much imagination to expand the definition of “usability” in this way. Beyond just the study of practices that make digital products easier to use, it’s reasonable to think of usability as a field that considers what’s in the best interests of the user. Clearly, there are best practices to be learned when it comes to limiting children’s time, signaling danger to parents, discouraging successive sessions over short spans, and even for encouraging physical movement. That all sounds like usability to me.
We’re moving past the stage in the evolution of our craft when we can safely consider its practice to be neutral, to be without inherent virtue or without inherent vice. At some point, making it easier and easier to pull the handle on a slot machine reflects on the intentions of the designer of that experience. If design is going to fulfill the potential we practitioners have routinely claimed for years—that it’s a transformative force that improves people’s lives—we have to own up to how it’s used.
This lengthy, thoughtful screed was inspired in part by an article that I wrote earlier this year for Fast Company called “Design Discourse Is in a State of Arrested Development,” the gist of which was to say that what gets written, read, discussed and lectured with regard to design is, on the whole, very shallow. I argued that that superficiality points to a systemic failure in design: an unwillingness to “ask tough questions,” and an inability to push the craft forward in the interest of both its practitioners and of its audience.
As publishers and key participants in the world of design discourse, Teixeira and Braga admit that they have played a part in perpetuating this environment. They write:
Last year, we published and shared 4,302 articles and links with the community — through Medium, our newsletter, our chatbot, our yearly trends report, Today, Journey, and many other channels.
In an extensive exploration of the subject, Teixeira and Braga examined every link they found on major online design forums (e.g., DesignerNews, WebDesignerNews, StackExchange UX, and Reddit UserExperience, Sidebar, Product Weekly, UX Curator, and UX Collective itself) for a month. “Every link shared between 12 Feb and 11 Mar 2018,” they say, “was put under the microscope, through the lenses of independence, honesty, breadth, and depth.”
They then plotted each article’s on a spectrum with “tactical” articles on one side (with templates, kits and tutorials at the extreme) and “strategic” articles on the other (with discussions of ethics, responsibility and impact). While acknowledging the subjective nature of the exercise, the results are nevertheless eye-opening: as seen in the chart below, the vast majority of the links fall on the “don’t make me think” end of the spectrum.
It’s clear that the currency of design discourse is really concerned with the “how” of design, not the “why” of it. As Teixeira and Braga write:
While designers tend to be skeptical of magic formulas—we’re decidedly suspicious of self-help gurus, magic diets, or miraculous career advice—we have a surprisingly high tolerance for formulaic solutions when it comes to design.
That’s a pointed criticism but, from my perspective, it’s also quite accurate. Rather than leaving that conclusion on its own, though, the essay tries to come to grips with, appropriately, why this is. Consistent with the habits of good designers, Teixeira and Braga undertake a bit of “user research” to understand how design content gets consumed, and who actually generates it. They even dig into one of the key paradoxes of an art form that is examined almost solely by its own practitioners: its highest functioning leaders usually can’t spare the time to write about their own perspectives.
The whole article is full of valuable insights like this but it’s worth reading for another reason alone: it shines a light forward for design discourse by first recognizing its deficiencies and then by modeling a way forward. Read it in full at essays.uxdesign.cc.