The point here is not to make yourself look stupid, rather, it’s to get at a basic understanding of how the world works from another person’s perspective. With regard to the example above, I’ve heard lots of responses to the “What do you mean by ‘fast’?” question. For some people, especially those with a technical background, “fast” means that pages appear quickly when you’re clicking around on a site. For other people it means that you’ve got some problems with your workflow. These people feel silly clicking all over your site to get things done, especially in comparison to those new cool Web 2.0 sites they’ve used.

So if you have a feeling in your gut that you don’t understand where someone is coming from, don’t be afraid to ask a “stupid” question. Get back to basics, it’ll help you see the world through the eyes of another.

Look at each decision you’ve made, and simply ask, ‘Why?’“

Links should be blue, you’ll decide. Next action: Why?

Each time we use the word MagicTouch in a headline, it should be followed by an ® symbol. Next action: Why?

A client will say to you, “I think it will look better if this text is center justified, rather than left aligned.” Next action: Why?

Stopping to ask why? will force you and others to think about the actual intended use of a feature. It will push you to think about user behavior, instead of random decisions. And most of all, it will teach you that you actually believe in what you’ve designed, because you’ll know you’ve thought it through. If at any point you can’t answer the Why? intelligently, you’ll know you have some rethinking and potentially redesigning to do.

This concept should be applied outside the world of design, as well. When you come to a decision, it’s never a bad idea to test it out with a well thought out Why?

In the end, it’s all about finding purpose. In everything, find purpose.

And with that message, I would like to share the news that I have decided to move on from ThoughtWorks. My time here has been tremendous and purposeful, but it is time for me to go try something new. If you read my blog via ThoughtBlogs, I invite you to subscribe to my RSS feed, because it likely won’t be displayed here much longer. Thanks, ThoughtWorks. I’ll miss you.

As I consumed the popular media, I began to think about the more pedestrian views out there. It is important to understand what the everyman thinks, even if one does not agree with him or her (and I certainly do not agree with many of the opinions out there). After all, it is only by understanding others’ points of view that we will ever get ourselves out of these international confrontations. Peace comes when people understand and interact with one another.

A great place to get at peoples’ opinions is the popular new communication tool: Twitter. Twitter allows users to post messages, opinions, and thoughts 140 characters at a time. Each post is a tiny glance at a person’s thought. If you’re not a member yet, you should give Twitter a try. It’s quite fun and addictive.

So, as I set out to glance at what people were saying about the situation in the Middle East via Twitter, I decided to build a tool that would help with this task. And so I did just that, with TwiddleEast.

Here's what TwiddleEast looks like

TwiddleEast allows you to quickly glance at what people on Twitter are saying about a few of the Middle Eastern countries in the news today.

Check it out, and I’d love to hear if it is helpful to you. If there is anything I can do to make TwiddleEast better, don’t hesitate to let me know, and while you’re at it: follow me or TwiddleEast on Twitter.

This afternoon I was convinced that it was time to get out. Time to persevere (against a zero-degree temperature) and try, at least a little, to get something done. So I packed my side bag and headed out to the gym. That’s when I met my hurdle: digging out the car.

I started the activity the way I normally do: by starting up the engine (because if it’s too cold for that to happen, then there’s no point in the rest) and blasting the defroster. I then brushed and scraped the car, and checked the tires to make sure they were in a good position to free themselves. Everything looked fine, and as I waited for my windshield to fully defrost I thought positively about how I would get out of my spot. I pictured the car rocking gently back and forth and then, almost comically, jumping out of its spot and onto the nice, soft, well-plowed street.

The ease of my vision was not to be in real life. I rocked my car plenty, but managed to get myself stuck and re-stuck three times. Yes, that’s right, I said three times. Each time I ran into my apartment building and grabbed the steel-headed shovel, ran back outside and cleared as much ice as I could away from the wheels. And each time I found myself stuck again, only to repeat the whole process.

Finally, in frustration, I decided to give up. This was enough of a workout for the day. Shoveling snow is not as easy as it may sound. You have to realize that that soft snowy powder that you may be picturing eventually turns into big, heavy boulders of ice and hard rocks. (This is why there are many heart attacks during winter…people forget how difficult it is to shovel snow.) As I surveyed where my car lay, I realized I was blocking an alleyway. So not only was I stuck and ready to give up, but I also had to do something to get myself unstuck.

Luckily, a nice man from the next apartment over had seen my struggle and came outside to offer a hand. After a bit of pushing he was unable to free me from the predicament. We talked about strategy for a few minutes, and then another man showed up. “Easy on the gas, real easy,” he said. Another couple of heaves and ten seconds later my car was free.

When I returned home a bit later after a drive to cool my insides down I found a nice parking spot that should be a bit easier to get out of. As I approached my apartment I spotted a car with its wheels spinning. With the driver accelerating, I pushed the car out of its spot. A few minutes later when I ran to my car to pick up the forgotten shovel, I spotted the man I had pushed out helping yet another stranger. As I passed he waved and said thanks, and I relayed my story of just an hour earlier. We laughed it off and shared a, “yup, it’s finally really winter again” moment.

This is what it’s like to live in Chicago. It’s a city that’s tough as it is soft. It’s a place where people push past and look out for each other. A place where we don’t interact much in the winter, but when it’s needed, people are glad to lend a hand.

This is where I live and despite the tough parts, I love when the gentle, helpful side of this city emerges. It’s like no other place I’ve lived.

And all you people are the heroes I’ve known
We’re staring off the edge into the unknown
We are not there yet, but we cannot go home
So we cry and we sing
Yeah I remember everything

How for once in our lives
We saw what we wanted and took a bite.
We picked the fruit from the tree, and it was ripe.
And it was ripe, and it was ripe, and it was ripe.”

- Ben Lee, “Ripe”

If you’re American, get out there and vote today. It’s your civic duty. We’re all counting on you. Thanks.

Google Chrome Design Comic

Comics have been a topic of discussion in the Interaction Design Community for a while now. With Scott McCloud providing the art for Google’s message, they really couldn’t go wrong. McCloud has quite literally written the book(s) on creating effective comics. (Of course, you can create your own design comics too, thanks to projects like Martin Hardee’s Design Comics.)

One thing that I’d like to applaud Google for with this comic is their use of actual Googlers as the narrators of the story. Naming names like this gives credit to the actual thinkers behind the work. All too often in the business world today, we hide individuals behind a big corporate brand. In this example, these Googlers will feel real ownership and responsibility for their product, and they’ll be motivated to continue working on the project even if (and when) they leave Google. Of course, I’d also like to call out the fact that no User Experience team members were named in this document, even in the section titled “Search and the User Experience.” This is strange, and I hope there was a User Experience team dedicated to this project.

And another thing Google did well here was in not trying to over-engineer their explanations of highly technical processes. They simplified their message down to bare essentials, and I felt enlightened after reading this document. Most technical documentation talks down to people, assuming that all the basics are already understood. Google removed some barriers to entry by explaining their new technologies in a way that almost anyone with a little technical know-how can understand. This is something almost every other open source project out there fails at. Technical documentation is far more than simply documentation…it’s an implicit invitation to take part in the experience.

Browser Threads Vs. Processes

At the end of the day, I’m really impressed at the quality of this documentation. I actually read the entire thing, which is much more than I can say about the technical documentation for any other software I use. Who knew that I could find the difference between multiple threads and multiple processes interesting?

Well done, Google. Now I just have to find a Windows computer…ugh. I swore off those things months ago…

I hope you noticed that, in fact, we can do all these things today. However, a mere 100 years ago, these questions would have been dismissed as pipe dreams by most people. But dreamers dream, designers design, technologists build, and before you know it, really difficult problems find solutions.

This is why I try to take the long view when thinking about design problems. Today’s technology is ephemeral, it will be gone before you know it. But when you find solutions to the big problems, those interactions can last for centuries. So the next time you start a project, instead of asking, “What would the UI look like to solve this problem?” (or even worse, “What will the architecture of the software look like?”) ask “What if we could ________?” And fill in the blank with a really challenging problem.

After all, if you’re like me, you didn’t get into technology to solve tiny little problems. You got into technology to make lives better & jobs easier. You got into technology because there are challenging problems to be solved. What if you solved them?

Thanks, The Onion. Happy Monday everybody.