• Skip to primary navigation
  • Skip to content
  • Skip to primary sidebar

Simplicity Rules

Adam DuVander on keeping it simple

  • About Adam

Law 4: Learn

December 7, 2006 by Adam DuVander

This is part of a series looking at John Maeda’s ten Laws of Simplicity.

“Knowledge makes everything simpler.”

One reason I really like the Laws of Simplicity is because each one is important to the whole package. When I first read this law, I thought it was a cop-out. As a Web developer, I accept at least a partial truth to the claim that people don’t read directions. At a glance, this law says, “just tell them how it is and suddenly it’s easier because they know now.”

Learning has to happen somehow. It’s not the responsibility of this law to say how that happens. Hopefully the other laws make the knowledge transfer implicit.

It’s also worth acknowledging how much our users already know. Most sites don’t need to explain how to click links or fill out forms. Instead, the basic navigation style and layout of sites are similar because that’s what the users expect.

To me, the law of knowledge says to consider what your users already know. Once you have a group on their current knowledge, you can use the other laws to help them learn what they don’t know.

I think of the small technical lessons I have given my father. Perhaps the biggest was copying and pasting. The next biggest might have been the shortcuts to copy and paste. Those small bits of knowledge create a much simpler experience.

Two years ago, The Wheeze encouraged me to read Web sites in a feed reader. Taking the time to learn that process greatly changed the way I consume information. Now I probably track five times the sites in half the time.

As these examples show, this fourth law of learning works in tandem with the third law, time. Once you know something, you save time, which directly equates to simplicity.

Portland WiFi blanket launched

December 6, 2006 by Adam DuVander

Yesterday marked the first-phase launch of Portland’s WiFi cloud by MetroFi. It’s a pretty optimistic plan that will eventually cover over 100 square miles. I couldn’t be happier.

Does it make my Portland WiFi site a little less relevant? Maybe. When I started it over two years ago, I listed about fifty spots. Now there are over 250 hotspots. Ubiquity was bound to decrease its relevance. Ubiquity is a good thing here.

Portland Mayor cuts the ethernet cable for MetroFi launch

While I wasn’t invited to the ethernet-cutting ceremony (seriously–they cut a cable instead of a ribbon), I know WifiPDX has played an important role in Portland’s wireless Internet culture. I’m proud to live in a city that is taking connectivity for everyone seriously. I get a few phone calls per week about WiFi and I have hated telling people that they can’t have WiFi at home without paying fifty bucks per month.

Now I don’t have to. We’ll see how the MetroFi quality is. We’ll see if ad-supported free service and a premium option is enough support. But at least it’s available. They’ve released version one and can always add features later.

As for WifiPDX, it is not closing its doors. To me, hanging out at a coffee shop on my computer isn’t so much about the free Internet as it is the place and people. Even though I have WiFi at home, I go to a coffee shop for the atmosphere.

While I write about what some might see as my site’s obsolescence, November marks the first month that over 3,000 people visited WifiPDX. That’s 150% growth since August. Not bad.

Law 3: Time

December 6, 2006 by Adam DuVander

This is part of a series looking at John Maeda’s ten Laws of Simplicity.

“Savings in time feels like simplicity.”

Web design gurus have preached this law since the mid-90s. Watch your file sizes! Beware the total site “weight!” they warned. These are still excellent strategies for savings time, though broadband penetration means we don’t have to be quite as militant.

Ajax has opened up a whole new time-saving tool bag. Using Javascript, developers can limit the apparent roundtrips to the server that require an entire page to reload when only a small portion has changed.

Click-Wait-Load Diagram

In reality there is still a roundtrip going on, but it happens in the background. And it doesn’t have to return the header graphic, navigation, and other items the user already is seeing. Instead, it returns the smallest amount of information needed, saving time.

Better yet, it feels like we’re saving even more time. With a traditional roundtrip, the screen goes blank for just an instant, but it feels longer. What simplicity really gets down to is perception. If it seems slow, then it can’t be simple.

Taking perception a step further, Ajax developers have added small animations to display during the short wait:
Loading animationProgress bar animationRecycle-like arrow animation
Here’s a whole gallery of them.

Of course, progress bars aren’t new. They existed on Expedia and their ilk well before Ajax was around. Travel sites didn’t invent them, either, as they’ve been a staple of slow desktop operations for years. Heck, maybe old school programmers got the idea from “please take a number” signs at the deli.

In all these cases, we have a glimpse of action. When the end is in sight, the wait seems shorter. The shorter, the simpler.

(What I’ve left out here, for simplicity’s sake, is a whole other side of time savings. Fill in the gaps yourself by considering how online banking has saved us all so much time.)

Law 2: Organize

December 5, 2006 by Adam DuVander

This is part of a series looking at John Maeda’s ten Laws of Simplicity.

“Organization makes a system of many appear fewer.”

This law comes down to basic cataloging. Find like elements and put them together. Maeda uses the ol’ screenwriter trick of placing one thought/item on an index card. Then the cards can be moved around until you find the right groupings.

BestPlaces categories
At BestPlaces we’re continually honing in on the best way to show all the data we have on every city and zip code in the US. The most important step was organizing the data into categories. To show air quality, average precipitation, and unemployment rate right next to each other would be confusing. Organizing them into health, climate, and economy sections goes a long way to simplifying what we’re showing.


USDA’s Haynet was able to boil their entire site down to two links: have hay and need hay.

Have hay? Need hay?

I’ve harped on this before as being too simple. My main beef with it is that it’s not a template that translates to other sites very well. When architects have emulated the Haynet approach, they lost something in their simplicity.

A later law does a good job of explaining my problem with Have Hay / Need Hay. As far as organization goes, one can’t get much simpler.

As I mentioned yesterday, Maeda explains many of his laws with continuums between conflicting factors. It seems to me that as we nudge one way with one law, we cause a reaction that moves other laws. It’s a delicate balance that should be embraced, because with the process comes simplicity. Organizing is a big part of that process.

Law 1: Reduce

December 4, 2006 by Adam DuVander

This is part of a series looking at John Maeda’s ten Laws of Simplicity.

“The simplest way to achieve simplicity is through thoughtful reduction.”

This is the crux of most simplification. If something is not needed in a site’s global navigation, for example, get rid of it. There is a reason that most home pages are not entire site maps. Showing everything is not the simplest way to show an interface.

Google is an overused example. Yet, I go to it here because it’s so appropriate. When they brought the bare page with only a search box to the Web, Yahoo!’s front page was essentially a site map. Thoughtful reduction, in this case, meant removing everything not related to the aim of searching. They even auto-focused the cursor to the input box!

That’s not to say Yahoo! doesn’t try.

yahoo-dropdown.png

They used to have a drop-down box with choices for what to search: The Web, In Images, In Yellow Pages, In Products. It went away earlier this year, probably because it wasn’t really that useful. Removing it (or rather replacing it with the version shown in the multi-goal search box) was thoughtful reduction on Yahoo!’s part, even if it was a bit superfluous in the first place.

Recently, Joel Spolsky wrote about the Windows Vista shutdown menu:

The fact that you have to choose between nine different ways of turning off your computer every time just on the start menu… Can anything be done? It must be possible. iPods don’t even have an on/off switch.

By reducing, Spolsky got down to one option: shutdown. I think he went too far and made the menu too simple when he removed the restart option. As many Windows users know, that is often the best solution to a wacky computer problem. Shutting down and starting back up usually involves pushing a button on the machine itself, which sometimes means crawling under desks.

Laws of Simplicity - Reduce continuum

Nevertheless, Spolsky’s process shows how thoughtful reduction is a great approach to simplification. Taking it too far is part of that process, too. Maeda uses continuums (like the one pictured here) to explain the give and take of finding the balance point. You know you’ve gone too simple when you realize it needs to be a little more complex. And you know it’s too complex when you can make it simpler without losing something necessary in the process.

  • « Previous Page
  • Page 1
  • …
  • Page 48
  • Page 49
  • Page 50
  • Page 51
  • Page 52
  • …
  • Page 85
  • Next Page »

Simplicity Series

  • Designing the Obvious
  • Paradox of Choice
  • Laws of Simplicity

Copyright © 2026 · Elevate on Genesis Framework · WordPress · Log in