This week’s episode of the Back to Work podcast with Dan Benjamin and Merlin Mann really struck a chord with me. In Scream, Poop, and Run they have a long discussion about an article by Jad Abumrad called The Terrors & Occasional Virtues of Not Knowing What You’re Doing. There is one part in particular, where Merlin talks about not listening to people who tell you what you can’t do, that I keep replaying in my head:

There are so many voices that you are going to hear — some of them actually outside your head — so many voices that you are going to hear about what you should be doing differently, what you’re doing wrong, what you’ll never be capable of, what you’ll always suck at, and you’ve got to not listen to those voices.

The people who constantly tell you what you shouldn’t do are typically really good at not doing things. And that is a virus they are very happy to spread. They are people who just don’t make stuff, they are people who don’t do stuff, and they are more than happy to try to pull the entire world down to their level of not making and not doing. And that’s something to watch out for. Because if you listen too much to all those other voices, they’ll eventually become your voice. And that’s the voice that’s going to be with you all the time.

That’s the voice you’ll go to sleep with, and it’s the voice you’ll wake up with, and if you listen to it too much, it’s going to drown out the tiny voices. And the tiny voices are like the little Will O’ the Wisps in Brave, these little blue lights, saying, “Try this way. Come this way. Come this way.” And those little blue lights — or the tiny voices — you’re only going to hear that if you’re not being drowned out by all the things that say that you’re not even worthy of having your own Wisps.

Those are very loud voices — especially if you make stuff for the Internet. It’s just always there — it’s a constant din of people telling you what you should be beside yourself. And that’s the worst advice in the world.

The whole episode is great. Have a listen.

Here is a good example that shows how we still have some work to do before we’ll be able to settle on a standard set of mobile design patterns. In the Facebook iPad app, a drawer slides out if you want to see comments on a status. But once that happens, two existing iOS patterns collide.

I always try to swipe the drawer away to get back to where I was. But, of course, iOS also has a “slide to delete” pattern, so instead of the drawer disappearing, the “Delete” button comes up on swipe. The way to dismiss the drawer is to tap in the greyed-out area.

This is certainly a tough problem to solve, so I’m not trying to beat up on Facebook. It’s just an example to show that we’ll have to work through a bunch of these types of colliding patterns before we can comfortably design for mobile using established guidelines.

Angela Riechers wrote a fantastic article for Imprint Magazine about the nostalgic elements that we increasingly see in all types of design — from Industrial Design, to Architecture, to Graphic and Web Design. In this excerpt from Has Nostalgia Become a Toxic Force in Design? she address the skeuomorphism in our digital interfaces:

Nearly every one of the iPhone/iPad’s built-in apps uses an icon that refers to an outdated, much earlier version of itself: the Frank Sinatra stand mike, the vintage tube television, the spiral-bound address book, the envelope. Yet many smartphone users are too young to have used most of these objects in real life (consider the inconvenience of carrying them around); the nostalgic design of the interface feeds upon a set of reconstructed memories divorced from the experiences that generated them, creating a culturally-shared yearning for lost golden moments. The latest iteration of Apple’s iCal looks like a desk blotter—an item that’s been obsolete since we stopped writing with fountain pens. Ask ten people under the age of 30 if they know what a desk blotter is or what it was used for, and see how many have a clue what you’re talking about. Nostalgic design serves as a kind of safekeeping, preserving images of beloved objects so they don’t completely disappear from the collective unconscious.

She goes on to point out the problem of this longing for the past:

Nearly all good design is aspirational, showing us that better possibilities exist, but using lost eras to project images of perfection seems unfair—we can never duplicate the past, no matter how hard we try.

Her conclusion is that we desperately need a renewed faith in the future, and it’s a message we all need to hear. It’s definitely worth reading the whole piece.

Frieze Magazine posted a great roundtable discussion about the relationship between design and social responsibility. Even though it’s good that “socially responsible design” is becoming more popular, there are also some pitfalls:

There’s a great quote from Brazilian Bishop Hélder Câmara: ‘When I gave food to the poor, they called me a saint. When I asked why the poor were hungry, they called me a communist.’ Everyone loves you for donating something beautiful to a community in need. It’s a good way to win design awards and can sometimes have a meaningful short-term benefit for a community in crisis. But charity work often does not address to the deeper roots and causes of conflict and inequity, and at its worse may even exacerbate a situation, providing the veneer of a solution where deep problems still exist, and creating complacency where there is the need for outrage, tough choices and hard work.

The debate about invisible design is heating up again, thanks to a recent interview with Oliver Reichenstein in which he said this:

Good design is invisible. Good screen design happens in the subatomic level of microtypography (the exact definition of a typeface), the invisible grid of macrotypography (how the typeface is used), and the invisible world of interaction design and information architecture. Minimum input, maximum output, with minimal conscious thought is what screen designers focus on. And just as type designers and engineers we do not try to find the perfect solution but the best compromise.

I’m going to assume that this tweet from Dan Saffer is in response to the interview, and not some amazing coincidence:

Good design isn’t always invisible. In fact, it can be stunningly, beautifully visible.

— Dan Saffer (@odannyboy) July 26, 2012

So, uh, which is it? Well, they’re both right — because I think they mean different things when they say “invisible design”. See, we talk about this stuff, but we rarely define the concepts before we do, and then we get into arguments and don’t even realize that we actually agree. So instead of just talking about invisible design, we have to discuss visible design as well, and how they’re different from each other.

When we talk about invisible design, I like Vitaly Friedman’s description in his excellent talk The Invisible Side of Design (my emphasis added):

Some things are so well designed that we don’t notice them any more. Our experience of them is invisible; almost beyond form and function… unless they break. The same holds true for Web design. Users stop noticing Web design if it works. Users keep noticing design if it’s broken, or when it gets in the way. Good design strikes a balance between elegance and invisibility. Invisible design relates to function and purpose, rather than appearance.

Invisible design is about the decisions we make about what goes into a product, what stays out, and how to get users through the experience as efficiently as possible. If those decisions are made well, and users can just do what they need to do without scratching their heads about where to go next — that’s when you get invisible design that works well.

But there’s also a striking visual layer to design that, in many cases, shouldn’t be invisible because invisible can be boring and soulless. Craig Grannell gives a good example of this in his article Office 2013 shows that user interface extremes aren’t the way to go:

The problem is, not all interface design scales, and when you go very minimal, interfaces can lose any sense of tactility and make it hard to focus. Peter Bright of Ars Technica’s shot of Office 2013 highlights that the opposite of Apple’s current design aesthetic isn’t necessarily any better. Acres of white space lead the eye to flick all over the design, making it hard to focus on the content (which is the smallish box on the right, with “This is an inline reply” in it). It’s unclear which components are buttons and which are content areas. Worse, there’s no sense of warmth at all. This feels like an email client designed to appeal to people bereft of emotion.

Look at sites like Slavery Footprint or MailChimp. There’s a very strong visual aspect to those designs, full of humanity and emotion. There is still an invisible side too — in MailChimp’s case, the functionality to create newsletters needs to be as invisible as possible — but it’s not an either/or situation. Invisible and visible design go hand in hand to create an appropriate product experience. In the case of Outlook 2013, there should be an invisible part of the design (the functionality you use to send email), but also a visible part that makes the software usable and relatable at more than a machine level.

I’m once again reminded of Matthew Butterick’s call to arms in Reversing the Tide of Declining Expectations:

Because what does design want from us, as designers? I think it wants us to take these items that are sort of mundane or boring on their own—like an annual report, or a website shopping cart, or a business card—and it wants us to fill them up. Fill them with ideas, and emotions, and humor, and warmth. Really everything that’s in our hearts and minds. Design wants us to invest these items with our humanity.

What it all comes down to is a term I first heard Karen McGrane use in her essay for The Manual called Ear Trumpets and Bionic Superpowers:

Designs that make technology completely seamless to the user often deserve admiration. But can we balance our desire for intuitiveness with a wider recognition that some tasks are complex, some interactions must be learned, and sometimes the goal isn’t invisible technology but appropriate visibility?

Instead of striving for purely invisible design, or design that is “stunningly, beautiful visible” but unusable, our aim should be to balance the decisions we make and the aesthetic we choose to arrive at a state of appropriate visibility. Now that’s good design.

They’re not always great at citing sources, and it’s not exactly the height of intellectual journalism, but I’ll admit: BuzzFeed’s publishing strategy is commendable:

We don’t show crappy display ads and we make all our revenue from social advertising that users love and share.  We never launched one of those “frictionless sharing” apps on Facebook that automatically shares the stories you click because those apps are super annoying. We don’t post deceptive, manipulative headlines that trick people into reading a story.  We don’t focus on SEO or gaming search engines or filling our pages with millions of keywords and tags that only a robot will read. We avoid anything that is bad for our readers and can only be justified by short term business interests.

Instead, we focus on publishing content our readers love so much they think it is worth sharing. It sounds simple but it’s hard to do and it is the metric that aligns our company with our readers. In the long term it’s good for readers and good for business.

That’s from an email that BuzzFeed’s CEO sent to employees, and it’s worth reading in its entirety because it’s such a good description of the principles that good online publishing is built on.

Earlier today a new design for Elezea went live. This is about the 5th or 6th redesign since I started the site, but it’s the first one that I think deserves a moment to stop and reflect a bit. With this redesign, I feel like the site finally grew up to become what it always wanted to be. I try to stay away from meta posts because I understand they’re mostly interesting to me, and no one else, but I trust you’ll forgive me for doing it just this once.

I had two major goals with this redesign:

• To have a design that’s completely focused on the reading experience.
• To improve site speed and performance dramatically.

With these two goals in mind, I asked my friend Alex Maughan to help me with designing and building a custom WordPress theme to accomplish these goals. He did an absolutely stellar job, and I can’t thank him enough. This design makes me happy. Thank you, Alex.

But let’s talk a little bit about each goal.

A design focused on reading

There is one single thought that became the driving force for what I wanted to accomplish with this design, and that’s Jeffrey Zeldman’s quote from 1999 (I’m afraid the original post doesn’t exist on Adobe’s site any more, so I’ll have to link to Zeldman’s discussion of it):

Most of all, I worry about web users. Because, after ten-plus years of commercial web development, they still have a tough time finding what they’re looking for, and they still wonder why it’s so damned unpleasant to read text on the web — which is what most of them do when they’re online.

I discussed this issue in detail in an earlier post called Please let this not be the future of reading on the web, so I won’t rehash everything again here, except to say – yes, it’s damned unpleasant to read text on the web.

And yet, that’s (finally) changing as more and more sites strip away all the fluff – and make their sites responsive. Speaking of Zeldman, his own site is a very interesting experiment to try to rectify this issue. Other sites that are doing a great job at providing good reading experiences include Contents Magazine, the iA blog, and Marco Arment’s blog. So I wanted a site that provides an enjoyable reading experience, regardless of device or situation. With that in mind, here are some of the reasons behind the design decisions we made:

• A header that explains what the site is about (set the context), then gets out of the way once you start reading.
• A typeface that’s elegant and focused on readability – we decided to go with Adobe Garamond Pro. (Yes, Typography Is The Foundation Of Web Design)
• A color scheme that not only fits the logo, but also feels similar to the calming Sepia schemes that many reading apps (like Amazon Kindle and Instapaper) provide natively.
• A sidebar that sits off to the right – not in your face, but there if you need it – and is focused on what I consider the main calls to action on the site: subscribing to article updates. Everything else is secondary, as it should be.
• My favorite feature: a responsive design that scales down well to small screens, to ensure a consistently pleasant reading experience on all devices. No matter how prevalent responsive design becomes, I think I’ll always see it as a kind of magic.
• And finally, there’s an appropriate space for one of the well-designed ads from the User Experience Ad Pack. These ads are not only relevant to the stuff I write about, it also covers my hosting costs. I recently switched to the more expensive (but much more reliable) mediatemple, and I’m very happy so far.

The end result is, I hope, a site that’s focused on words, ideas, and readers. As it should be.

Improved performance

In a recent post I said the following:

I often wish I could move all my link-sharing off Twitter and onto this site, but I know that’s not really possible, because the readership isn’t quite there yet. But I much prefer not just tweeting a link, but also adding some thoughts, or even just trying to set the context so people can decide if it’s a link they would be interested in, or not.

I mentioned this to Alex, and said that if we can get the site to be extremely fast, I might be able to start moving all my link sharing here. He saw that as a challenge, and went to work… So what we have now is the following:

• The site is now only a fraction of the size it used to be. It should also have faster server response times from a PHP processing and DB query point of view, as there is much less server side processing required to generate the site.
• W3 Total Cache handles all the site’s caching.
• I use Amazon Cloudfront as CDN.
• I also run CloudFlare on top of everything, and I’m really happy with that service so far.

Ok, I think I’ve rambled on long enough. The TL;DR of this whole post is this. I’m really excited about this design, I hope you like it, and thank you Alex!

Angela Baldonero in Just Say No:

We’ve all seen the all-important and all-knowing executive team. The team that has all the answers and yet isn’t able to execute. I’ve seen too many executive teams where personal relationships and politics are the real business drivers behind-the-scenes. Business is done over cocktails, after hours and not in broad daylight. Personal agendas trump team goals. People smile and nod politely in meetings, then leave the meeting and corner the CEO to say what they “really think.”