What is a Microinteraction?

I’ve been asked What’s a Microinteraction? a few times lately, so here’s a brief excerpt from the draft of the first chapter of my new book, Microinteractions.

Microinteractions are contained product moments that revolve around a single use case. In other words, microinteractions have one main task. Every time you change a setting, sync your data or devices, set an alarm, pick a password, log in, set a status message, or favorite or “like” something, you are engaging with a microinteraction.

…Even though we’re surrounded by microinteractions every day, we don’t usually notice them until something goes horribly wrong…but microinteractions are, despite their small size and near-invisibility, incredibly important. The difference between a product you love and a product you tolerate is often the microinteractions you have with it.

Microinteractions are the details of a product, and details, as Charles Eames famously said, aren’t just the details; they are the design. Details can make make engaging with the product easier, more pleasurable—even if we don’t remember them. Some microinteractions are practically or literally invisible, and few are the feature that you buy a product for (although many apps and devices are created around a single microinteraction; see Chapter X); instead, they are usually pieces of features, or the supporting or so-called “hygiene” features. For example, no one buys a mobile phone for the mute feature, but as we’ve seen, mute can create all sorts of experiences—for good and bad.

Think about it: Almost all operating systems, be they mobile or desktop, do basically the same things: install and launch applications, manage files, connect software to hardware, manage open applications/windows, etc. But the difference between operating systems—at least from a user’s perspective—are the microinteractions you have with it on a daily, even hourly, basis.

New Book: Microinteractions

I’m very pleased to announce that I have a new O’Reilly book coming out in May 2013 called Microinteractions: Detail-driven Product Design. What’s it about and what are microinteractions? Well, I’ll tell you.

“The details are not the details. They make the design.” Charles Eames

The difference between a good product and a great one are its details: the microinteractions that make up the small moments inside and around features. How do you turn mute on? How do you know you have a new email message? How can you change a setting? All these little moments—which are typically not on any feature list and often ignored—can change a product from one that is tolerated to one that’s beloved. They are the feel part of “look and feel.”

The book provides a new way of thinking about designing digital products: as a series of microinteractions that are essential to bringing personality and delight to applications and devices.

Microinteractions are single- or few-use-case engagements that are either on the edge of a product or contained within a bigger feature. You engage with microinteractions every time you log in, pick a password, favorite or like an item, or set a status message.

Microinteractions are made up of five parts: triggers, controls and affordances, the interaction rules, feedback, and states/modes/loops. Each part gets its own chapter, as does the overall Microinteractions Model.

Now all that’s left to do is write it!

The website is going up soon, and it’ll eventually contain excerpts and book news. Stay tuned.

FOO Camp 2012 Report

After many years of enviously watching friends attend, I was thrilled to be invited to FOO Camp this year. In case you don’t know what that is: FOO stands for Friends Of O’Reilly, and it’s an annual, invite-only “unconference” of ~300 technologists, designers, scientists, journalists, writers, and others at the O’Reilly Media compound in Sebastopol, California. The list of attendees every year is impressive and intimidating, and as soon as I was invited I began stressing about what I would talk about and whether I’d be in completely over my head. (Talking to other first-time attendees, which make up about 50% of every FOO Camp, this is a very common experience.)

FOO Camp is also about camping: you bring a tent or a sleeping bag and camp on the lawn or inside the O’Reilly offices (!). I brought my gear and camped on the lawn. The camping also made it all have an air of informality, which helped lower the intimidation factor.

The “un-” part of the conference means that none of the content is programmed before people arrive. You show up and sign up for a slot to speak about something that interests you or to demo something you’re working on. I came with one idea, but abandoned it to do another (How To Get Your Project Mojo Back, which I’ll detail in another post). The unconference format also means Powerpoints are discouraged, so you are leading or participating in a conversation, often with very brilliant, opinionated people. Getting a point in can be a challenge, as can getting people who are used to being the Smartest Person in The Room to keep quiet and let others talk. The loose, unconference-style made for some failed sessions, but also some great ones. I’d love to see one of the big design conferences try it.

At any given point, twelve (maybe more?) sessions can be going on, so it can be hard to choose among them. (It’s pretty unlikely anyone’s schedule looked the same.) Here’s what I ended up going to, and this was I’m sure in no way typical, although it does hint at the breadth of sessions:

  • Medieval Manuscripts
  • The Future of Memory
  • Cloud Robotics
  • Toys as Tools for Empathy
  • Massive Sensor Data
  • Physical Artifacts in Digital Media
  • New UIs for Making Things
  • What Are You Reading?
  • Stop Drawing Dead Fish

A lot of the conference takes place outside the sessions, with discussions going on until late at night. (I got about 4 hours of sleep each night.) It’s not unusual to find yourself (as I did) at breakfast with a tech titan or to meet your childhood hero (in my case this was Steven Levy, author of Hackers, one of the books that got me interested in computers in 1984.)

There were a few major themes that kept emerging for me. The importance of thresholds was one, especially understanding when there are hidden thresholds that cause something (data, feedback, understanding, emotion, technology) to act unlike it did previously. A return to physicality was a third: how can we make objects reflect the content/data they contain? And objects helping other objects was another. What data can other objects via an Industrial Internet pass along to other objects to make them work better?

I returned with a head-full of ideas. I likened my brain to the Big Dog robot that had been kicked but was trying to right itself and keep moving. But it was an amazing experience, one I hope to have again another year. Thanks to O’Reilly for having me!

Designing Devices: The eBook

I’ve collected and revised the essays I wrote on the Designing Devices is available now from Amazon, for the low low price of $3.99 USD or €3.

Reviews from Twitter

“Designing Devices is great.” —Ben Bashford

“Dan Saffer’s short book on designing devices is very worth reading, even if you’re not actually designing devices.” —Basil Safwat

“Designing Devices is a great read. Highlights device design challenges and how to work through ‘em.” —Karen Kaushansky

Buy Designing Devices on Amazon

My 2011 Bibliography

FICTION
The Quantum Thief, Hannu Rajaniemi
The Dervish House, Ian McDonald
A Feast for Crows, George R.R. Martin
A Dance with Dragons, George R.R. Martin
Anathem, Neal Stephenson
Wolf Hall, Hilary Mantel
Zone One, Colson Whitehead
The World at Night, Alan Furst
Stories of Your Life and Others, Ted Chiang
Blindsight, Peter Watts
His Majesty’s Dragon, Naomi Novik
Throne of Jade, Naomi Novik

PHILOSOPHY
Pragmatism, William James
Status Anxiety, Alain de Botton

BIOGRAPHY AND AUTOBIOGRAPHY
Steve Jobs, Walter Isaacson
How to Live: Or A Life of Montaigne in One Question and Twenty Attempts at an Answer, Sarah Bakewell
The Enemy, Christopher Hitchens
Here, There and Everywhere: My Life Recording the Music of The Beatles, Geoff Emerick
You Never Give Me Your Money: The Beatles After the Breakup, Peter Doggett
The Cello Suites: J. S. Bach, Pablo Casals, and the Search for a Baroque Masterpiece, Eric Siblin
A Jane Austen Education: How Six Novels Taught Me About Love, Friendship, and the Things That Really Matter, William Deresiewicz

DESIGN
The Design of Design: Essays from a Computer Scientist, Frederick P. Brooks
Tapworthy: Designing Great iPhone Apps, Josh Clark
Designing Mobile Interfaces, Steven Hoober and Eric Berkman

COGNITION
Incognito: The Secret Lives of the Brain, David Eagleman
The Ego Tunnel: The Science of the Mind and the Myth of The Self, Thomas Metzinger

GENERAL NONFICTION
Arguably: Essays, Christopher Hitchens
Griftopia: A Story of Bankers, Politicians, and the Most Audacious Power Grab in American History, Matt Taibbi
Little Bets: How Breakthrough Ideas Emerge from Small Discoveries, Peter Sims
Medici Effect: What Elephants and Epidemics Can Teach Us About Innovation, Frans Johansson
The Price of Everything: Solving the Mystery of Why We Pay What We Do, Eduardo Porter
Spark: How Creativity Works, Julie Burstein
Mindfire: Big Ideas for Curious Minds, Scott Berkun
59 Seconds: Change Your Life in Under a Minute, Richard Wiseman
Manhood for Amateurs: The Pleasures and Regrets of a Husband, Father, and Son, Michael Chabon
The Last Lecture, Randy Pausch
First We Read, Then We Write: Emerson on the Creative Process, Robert D. Richardson
Pulphead: Essays, John Jeremiah Sullivan
The Creative Habit: Learn It and Use It for Life, Twyla Tharp

RELATED: My 2010 Bibliography

My Top Ten Albums 2011

As with previous years, my criteria for the Best Albums of the Year are replayability (I still listen to this album, and years from now, I predict I’ll still be listening to this album) and non-skipability (I don’t skip over many tracks). Your mileage may vary.

10. Move Like This, The Cars. Like 1986 preserved in amber.

9. Noel Gallagher’s High Flying Birds. A pure slab of 1990s BritPop.

8. We Are The Tide, Blind Pilot. Not as good as their first album, but melodic and thoughtful. Music for a Sunday afternoon.

7. Burst Apart, The Antlers. If Radiohead still made rock albums, they might sound like Burst Apart.

6. Celabrasion, Sleeper Agent. This album is like the bouillon cube of indie pop music from the last 25 years. Echoes of everything from the Pixies to The White Stripes is in here.

5. The Head and The Heart. Soulful, singable. “Rivers and Roads” kills me every time.

4. Torches, Foster The People. Leave aside the ubiquitous and overplayed “Pumped Up Kicks,” and you’ll find a record filled with hooky songs worth your time like “Houdini” and “Don’t Stop.” A party album.

3. The King is Dead, The Decemberists. The Decemberists return to form by taking an alt-country tack. Harmonica does them good.

2. The Mistress, Yellow Ostrich. The first time I listened to this album, I was like, What are they doing? Yodeling? Throat singing? But then, wow, you get it. Distinctive sound, great hooks. I defy you to listen to “Hahahaohhoho” twice without yodeling yourself.

1. Um, Uh, Oh, Say Hi. This is the album I always knew Say Hi would make one day. Every song is a gem. Singable, memorable, alternately uplifting and heartbreaking. “Take Ya Dancin’” should have been a huge hit. A real keeper. Sad this hasn’t gotten the recognition it deserves.

Disappointments: Let England Shake, PJ Harvey; The Whole Love, Wilco; The King of LImbs, Radiohead; Bon Iver, Bon Iver; Mountaintops, Mates of State. And yes, I know all these albums are on various Best Of lists. They just didn’t do it for me.

Related: My Top Ten Albums of 2010, 2009, 2008, 2007, 2000-2009, 1990-1999.

My Favorite Design Articles 2011

The best articles on design or the design field I came across in 2011 (in alphabetical order by author):

Blessed are the Toymakers, Tom Armitage

The best toys have hidden depths. The best toys are all super-simple on the surface; super-obvious. They let you know exactly what you ought to try doing with them. But as you explore them, you discover they have hidden depths. And: hidden affordances. Spaces for imagination to rush in. Toys allow you to play games, inventing rules that make the toy more fun, not less. Toys allow you to tell the stories you imagine, not that are baked into them.

From Snarky Truth to Reasoned Explanation, Faruk Ateş

You want to know how to get more women and minority members in your field of work? Stop fighting and arguing against people who are asking for more women and minority members to be recognized. It is precisely these fighting efforts ones that make those groups feel unwelcome.

Emoticomp, Ben Bashford

Interaction designers are used to using personas (research based user archetypes) to describe the types of people that will use the thing they’re designing – their background, their needs and the like but I’m not sure if we’ve ever really explored the use of personas or character documentation to describe the product themselves. What does the object want? How does it feel about it? If it can sense its location and conditions how could that affect its behaviour? This kind of thing could be incredibly powerful and would allow us to develop principles for creating the finer details of the object’s behaviour.

Requirements-Driven Software Development Must Die, Fred Beecher

Requirements-driven software development fails mainly due to communication issues. Huge spreadsheets of detailed requirements, by themselves, are simply not an effective way to convey what an interactive system needs to do and how users need it to work. What does work, however, is validating those requirements with an interactive prototype.

7 Things Michael Bierut Loves About Design, Michael Bierut via Helen Walters

Asked to create a logo for the Frank Gehry building, Bierut came up with a series of solutions that the client absolutely hated. Having presented one idea, he recalled, “they were supposed to see it and ask ‘how can we thank you?’ Instead the question was ‘is this supposed to make us feel nauseous?” In the end, the company founder Michael Tilson Thomas sent a series of his own scrawled ideas. Usually a cue for designers to feel uppity and upset that a client is trading on their toes, Bierut welcomed the input, and used it to come up with the final (gorgeous) solution.

Seven Things Designers Can Learn from Stand Up Comics, Michael Bierut

Good comedians experiment constantly. Every time they test a new joke, they risk bombing. That’s why they’ll try out new material in smaller venues, polishing pieces in front of live audiences: they need to hear what’s working and what’s not working. Seinfeld admits that when he was starting out, “I was hitting 500. I would have a good show and a bad show, a good show and a bad show.” His very first show was bad. “But success wasn’t my objective.” He was desperate to simply be on stage, and was willing to risk failure every other night to get there. Designers take risks for the same reasons. Trying something new means not being sure of the outcome. But it’s the only way that anyone working in a creative field can hope to make progress. Ambition is a strong enough antidote to fear. Louis C.K. remembers how he idolized good comics: “I wanted to be one of them, and I didn’t care if I sucked at it.”

What The Telephone’s Unbeatable Functionality Teaches Us About Innovation, Stefan Boublil

Design has become almost useless to mankind since so few people pursue single-mindedness as a foundational purpose, but would rather purposelessly chase multi-functionalism down a dark and long tunnel that may well lead to magazine covers, but to little else.

How to Lead Clever People, Karen Christiansen and Rob Goffee

You touched on the fact that unlike artists or musicians—who can thrive on their own—clevers actually need organizations to thrive. Why is that?
Typically, they need to work with other clevers in order to generate new products and knowledge. In many cases they are actually motivated by working with others who may be even cleverer than they are. We talk about Google in the book. I went to visit some of the people there at the headquarters in California. Not surprisingly, they are hiring the brightest postdoctoral students and researchers in the world; that’s who gets to work at Google. And guess what the first thing they notice when they arrive is? ‘Everyone here is cleverer than me!’ This is motivating for them, because clevers thrive when they feel surrounded by people just the same or even cleverer. That’s one of the reasons they need organizations. There are also more pragmatic reasons: they also need resources and they need organizations as a platform to achieve recognition.

Convergence 2.0 = Service + Social + Physical, Hugh Dubberly

Convergence 2.0 recognizes that interactive multimedia exist within a networked world and depend on networked services. It recognizes that most services have a social component. And it recognizes that people are rooted in the physical world and networks are increasingly connected to things. Convergence 2.0 integrates interactive multimedia with internet-based services, social networks, and the physical world.

Fundamental Design Truths, Uday Gajendar

Every design involves compromises, trade-offs, constraints : This is just a hard fact of design practice, period. You can’t get everything 100% due to the social and political complexities of…working with people :-) The pragmatics of any design problem require understanding of and wrestling with constraints (technical, commercial, social, etc.), negotiating various trade-offs (since no design is perfect, see above) which then forces critical debates about what is most important (prioritizing content, functionality, features, so forth) to the product & user & business. This debate is what should lead to a well-guided strategy adapted over time. The ability to artfully compromise to achieve goals for all stakeholders is at the heart of any design.

Copycats, Matt Gemmell

The issue is that real design jobs aren’t about creating something absolutely new—instead, they’re about innovation. The etymology of the word ‘innovation’ means something like “renewing”, or changing an existing thing by adding something new or doing something differently. Not a clean-cut, start-from-scratch scenario – that’s not what innovation is, and that’s why it’s hard.

Hand waving and the “real work” of design, Elizabeth Goodman

“Hand waving” is a pretty apt description of what interaction designers do with clients. Typically, those meetings are intended to review the course of the project and decide what to do next. These decisions are generally based on representations of the planned future system, such as wireframes, visual comps, flows, site maps, paper sketches, etc. The problem is that there’s an inevitable gap between representations of what is to be built and the experience of the finished product. This is most obvious when you think about the difference between static wireframes and interactive systems. But the problem lies deeper. If you see the goal of interaction design as supporting human goals and activities through various interactions between humans and machines, then even a clickable prototype will not match the experience of the live system. Imagine Amazon without the recommendations, or World of Warcraft without the thousands of players per server. Hand waving—ie, a combination of verbal explanations and evocative body movements—is a way to bridge that gap between intermediate representations and the experience of the built system. Hand waving supplements visual representations in order to make up for what they lack – interactivity, movement, emotionality, etc.

Minimal Viable Personality, Grimlock

PERSONALITY IS API FOR LOYALTY. NO ONE CARE WHICH BORING STRANGER IS NEXT. BUT ALWAYS WANT FRIEND NEXT.

Portable Cathedrals, Dan Hill

Each mobile phone handset is not a mere product, perhaps like the other products that have traditionally adorned the pages of this magazine—as a chair is, or a lighting fixture is. Instead, each handset is a play in a wider global contest, a node in logistics networks of immense scale and complexity, a platform for an ecosystem of applications, an exemplar of the internet of things, a window onto the daily interactions of billions of users, of their ever-changing personalities and cultures, a product that consumers traditionally consider the most important in their possession, after the keys to their home.

The phone is an intimate device, not simply through its ubiquity and connectivity, its relationship with the body. While objects have long been cultural choices and symbolic goods, the mobile phone, being the most personal connection to the internet, is a device for generating symbolic goods, a vehicle for culture, a proxy for the owner’s identities. It is vast business and cultural phenomenon, all at once.

The Robot-readable World, Matt Jones

Computer vision is a deep, dark specialism with strange opportunities and constraints. The signals that we design towards robots might be both simpler and more sophisticated than QR codes or other 2d barcodes.

How Print Design is the Future of Interaction, Mike Kruzeniski

The literal analog affordance is no longer necessary, and yet, it’s the default path that so many interactive experiences follow. We don’t need to make an eBook look like a book for people to understand how to use it. The book isn’t the cover and binding, it’s the images and the text that make the story. Similarly, a movie doesn’t need to look like a DVD on a shelf to understand that it belongs to a collection, and an audio mixer doesn’t require cables and knobs to be capable as a tool, and a Notebook does not require leather and a spiral bind to be familiar. In the early days of interaction design when software concepts were best explained through heavy handed metaphors, the familiarity of these objects and textures was appropriate. However, the rendering of artifacts has outlived its usefulness as the definitive approach to UI design. As Designers we should be critiquing it for what it often is: shallow, meaningless, and often distracting from the information it surrounds.

Checklist Thinking for UX Professionals, Greg Laugero

Key to success is public visibility of the connections among deliverables. For instance, when showing page flows, start by showing the user stories as a setup for the flows. Or if you are developing user stories, start by reminding everyone of the personas and scenarios. This ensures you have the best chance of making sure the next deliverable is as complete as possible. You also can more readily identify new scenarios, requirements, and user stories without feeling defensive, or like you missed something. If you’re doing this right, you should start to hear your clients say, “This sounds like a new user story!” when new functionality inevitably comes up.

Why Angry Birds is So Successful and Popular: a cognitive teardown of the user experience, Charles L. Mauro

What makes a user interface engaging is adding more detail to the user’s mental model at just the right time. Angry Birds’ simple interaction model is easy to learn because it allows the user to quickly develop a mental model of the game’s interaction methodology, core strategy and scoring processes. It is engaging, in fact addictive, due to the carefully scripted expansion of the user’s mental model of the strategy component and incremental increases in problem/solution methodology. These little birds are packed with clever behaviors that expand the user’s mental model at just the point when game-level complexity is increased. The process of creating simple, engaging interaction models turns out to be exceedingly complex. Most groups developing software today think expansion of the user’s mental model is for the birds. Not necessarily so.

How to Pick the Right Clients, Mike Monteiro

Over the years the one constant that we’ve been able to rely on is that how a potential client behaves in the business development process is EXACTLY how they will behave during the project. Trust your gut. If they’re slow to return your calls now, while they’re trying to engage you, they’ll be just as slow later. If gathering requirements or success metrics is hard, then gathering feedback will be just as hard, if not harder. If biz dev turns into a May Day parade of red flags then disengage. You will not be able to do good work, and neither you nor the client will be well-served.

The A-B-C of Behavior, Jodie Moule

We all seem to be talking about changing behaviour through good design…but changing behaviour is actually really hard. Working as a psychologist in a detox unit at the start of my career has admittedly shaped my view of what it takes to change someone’s behaviour; and whilst I learnt it certainly isn’t impossible, it often takes time. Combine this with the fact that most human behaviour is not considered to be overly planned, with ‘conscious thought’ playing, at best, a small role in shaping our choices…things start to become a little tricky for us as designers. So how do we start to make sense of what influences someone to change their behaviour, given we are often charged with creating designs that are ultimately intended to encourage, if not drive, some form of behaviour change?

Act First, Do the Research Later, Don Norman

Today we teach the importance of doing design research first, then going through a period of ideation, prototyping and iterative refinement. Lots of us like this method. I do. I teach it. But this makes no sense when practical reality dictates that we do otherwise. If there is never enough time to start with research, then why do we preach such an impractical method? We need to adjust our methods to reality, not to some highfalutin, elegant theory that only applies in the perfect world of academic dreams. We should develop alternative strategies for design.

Post-rationalization is An Innovator’s Best Friend, Adam Richardson

It is one thing to have the idea, quite another to understand its possibilities and implications. Some lightning bolt inspirations are indeed junk, but some of them really strike at something valuable. It’s just not always clear what that value is.

The Metaphor of The System, David Sherwin

The holy grail for any product or service designer is to be able to elegantly describe the metaphor of the system, then prove it out through usage scenarios. In some design presentations, it can take a single word or phrase to eloquently connect key moments in a system’s information architecture, interaction design, and visual design. When you encounter a system design with a compelling, unifying interaction metaphor, you can often detect that metaphor through the “iceberg tips” of wireframes, prototypes, or animatics. And when users interact with the system in testing, they often react to how those details weave together into a (hopefully) cohesive whole.

Bless The Toolmakers, Robin Sloan

So I wish more people were making tools for a specific creative purpose rather than for general consumer adoption. I wish more people were making tools that very intentionally do not scale—tools with users by the dozen. Tools you experience not through a web signup form, but through pathbreaking creative work.

I guess I want fewer aspirational Apples and more Pixar wannabes.

Creating Great Design Principles: 6 Counter-intuitive Tests, Jared Spool

Great design principles help designers learn more about their design and make critical decisions about what they’re building.

The Ten Principles of Interaction Design, Chad Vavra

To steal a metaphor from E.L. Doctorow, “[Interaction Design] is like driving a car at night. You can only see as far as the headlights, but you can still get to your destination”. When a task seems too big, start by picking two things, like a page and a button. Establish their relationship and interaction. Once that is done, pick something else that relates and keep going. Everything will come together thanks to the brain’s natural ability to spatially model the world.

A Brief Rant on The Future of Interaction Design, Bret Victor

Pictures Under Glass is an interaction paradigm of permanent numbness. It’s a Novocaine drip to the wrist. It denies our hands what they do best. And yet, it’s the star player in every Vision Of The Future.

How Much Design is Too Much Design?, Khoi Vinh

If you look across the digital landscape, the most exquisitely designed user interfaces and the most comprehensively designed user experiences are rarely the most successful. On the other hand, the most successful network products make good use of design but are usually not high watermarks for design execution. Flickr and Facebook, to name two, are both very well-designed but employ only just enough in the way of intricately polished user interface elements and highly controlled layouts to succeed, and stop short of over-managing their details. Products like these are savvy enough to allow sufficient room for a user to live within them, to flex his or her muscles and breathe freely within the product’s architecture. They’re also the result of considerable iteration and improvisation, and sometimes they show that fact almost baldly in their patchwork agglomeration of mismatched features. No one would call them beautiful but they work phenomenally well and users love them.

You Are What You Eat, Trent Walton

Eat one meal, then another, and over time that stuff becomes who we are. It’s used to heal skinned knees, grow fingernails, and rebuild tired muscles. I find that thinking of work in a similar fashion can be used to one’s advantage. When a job is done, we’re left with experience, new skills, and a sharpened perception. Do work that you enjoy so you can be good at what you love.

Our Jobs in Cyberspace: Craft Vocabulary vs. Storytelling, Jeffrey Zeldman

But the longer we practice, the more intuitive our work becomes. And as it becomes more intuitive, it disconnects further and further from language and constructs.

Any other article that should be on the 2011 list? Note it in the comments!

N.B.: Either women should write more about design, or I should be reading more of their writing. Woefully under-represented on this list. Who should I be reading?

Related: See my 2010 picks

My Top 25 Albums 1990-1999

25. Odelay, Beck (1996)

24. Nevermind, Nirvana (1991)

23. OK Computer, Radiohead (1997)

22. 69 Love Songs, The Magnetic Fields (1999)

21. Little Earthquakes, Tori Amos (1991)

20. Urban Hymns, The Verve (1997)

19. What’s The Story Morning Glory?, Oasis (1995)

18. Keep It Like a Secret, Built to Spill (1999)

17. Whatever & Ever Amen, Ben Folds Five (1997)

16. All This Useless Beauty, Elvis Costello (1996)

15. Garbage, Garbage (1995)

14. Elastica, Elastica (1995)

13. Zooropa, U2 (1993)

12. Doubt, Jesus Jones (1991)

11. 14 Songs, Paul Westerberg (1993)

10. Together Alone, Crowded House (1993)

9. Never Loved Elvis, The Wonder Stuff (1991)

8. Goodbye Jumbo, World Party (1990)

7. Exile in Guyville, Liz Phair (1993)

6. Electro-shock Blues, Eels (1998)

5. Nirvana Unplugged, Nirvana (1994)

4. Celebrity Skin, Hole (1998)

3. The Bends, Radiohead (1995)

2. Achtung Baby, U2 (1991)

1. Different Class, Pulp (1995)

In Praise of “Moving Stuff Around”

I was on my fifth revision of a search screen. (In my defense, it was a complicated search, with lots of variables.) The client said to me, in what might be my favorite comment of all time, “But you’re just moving stuff around!” Yes, I admitted rather sheepishly at the time, I was doing just that.

After the meeting ended, I realized I had no need to feel embarrassed. “Moving stuff around” is a lot of what design does: providing structure, hierarchy, and cues for understanding via positioning. But without justification and explanation, it can look like just fiddling.

I remembered this anecdote when I saw this 1972 interview with the legendary Charles Eames, in which he offers up his definition of design as:

A plan for arranging elements in such a way as to best accomplish a particular purpose. [emphasis mine]

If Charles Eames can put arranging elements aka “moving stuff around” as the core activity of design, then so can I. There is a value in putting objects such as controls into an understandable configuration. This is, in fact, the exact service many designers provide. Embrace it.

Never Waste a Project Lull

The nature of project work is that there are often periods of inactivity—both during the project (while waiting for feedback, for example) and between projects. It’s easy to piss away these lulls—you’re exhausted from doing the project after all—but you can also use the time productively by hunting and gathering.

Hunting involves finding new experiences to fill up the creative tank. The best creative practitioners are often those who can draw ideas from other fields, to make disparate connections to find solutions. Trying something different, even if it is just a new restaurant a little farther away, can provide new ideas, new stimulus. “Too often, we fail to consider the ways in which our surroundings constrain our creativity,” writes Jonah Lehrer. Doing or seeing something new stretches our creativity and gives us more raw material to work with when we return to work. You don’t have to skydive or travel to Bhutan, you just have to experience something not usually in your path. Whatever you do, don’t just sit at your desk, mindlessly surfing the internet. “We don’t know where we get our ideas from. We do know that we do not get them from our laptops,” notes John Cleese. Exactly.

Gathering involves reflection, thinking about the work that has already been done and figuring out the lessons learned. Especially if you write your thoughts down, gathering gives you another source of raw material: for blog posts, for presentations, and just for understanding your own work. Sometimes a pause lets you examine not just what, but how you did something, and why. (Definite shades of Donald Schön’s The Reflective Practitioner here.) If you can’t reflect on your work, and in particular the mistakes you made while doing your work, you won’t grow.

Everyone fixated on the 10,000 hours of practice to become an expert that Malcolm Gladwell illuminated in his Outliers book. But what he pointed out (and that everyone forgot) was what that what you did during those 10,000 hours mattered. Practice entails doing an activity, then honing it through reflection. You can do an activity for 10,000 hours and still suck at it if you’re not thinking about what you’re doing, then correcting your mistakes. A project lull is a perfect time to do this sort of gathering.

So yes, while you could dull yourself with ‘net surfing, YouTube watching, and general goofing off (all of which has its place as well), you could take some small steps to better yourself, so that when project work resumes, you’re ready.