Archive for the 'rambling' Category

Format for things that need format, freedom for those that don’t

Wednesday, May 18th, 2011

In our ever-so-digital world, it’s hard to think outside of the standard formats and metaphors that are presented to us. Presentations require slides, and so our presentation tools use slides as their metaphor. Emails require big and small blobs of text, and so the tools allow for that. The hard part, I find, is knowing when and how to ditch the metaphor.

Sometimes it’s good to structure your presentation with a bunch of blank slides and one or two diagrams sprinkled in. Sometimes the format of the meeting should be to come up with the end-goals first, rather than diving in to solve individual problems. And it’s even ok to pop images and videos into email, as long as they support the point.

Don’t try to mold everything to a particular format. Think about the medium, the message, the inputs, the expected outputs, and most of all, the people. And consider all of this all the time. Before every email. Before every presentation. Before every conversation.

From here on, that’s my goal.

On Risk and UI Design

Sunday, May 15th, 2011

Most designers and businesspeople are reticent to stir the pot when they’ve got a good thing going. When you’ve got thousands or even tens of thousands of people visiting your site each day, why take the risk of making a potentially shocking change? It makes little sense, right?

Well, that certainly makes sense if you’re working for an already established consumer web product (like the Googles and Amazons of the world). But for the up-and-comers like you and me, most users are yet to see the site or tools we’ve built when you think of the long-term. Keep this in mind when that angel on your shoulder is keeping you firmly planted on the side of safety. Give that devil the nod and try out a little risk. It could be well worth your while. I know I know I know, it’s trite, but this is totally true:

I’ll refrain from Justin Timberlake scenes from here on.

My point is a little different, though. Here’s what I’m thinking: Just because you’ve found a model that works doesn’t mean it is the only way forward. You already know this intuitively if you’re doing your job as a designer, but at the same time taking the leap is scary. I say go for it. Go for it, measure it, and change it back if you have to. Yes, people will complain, but most of the people who will use your site don’t even know you exist yet. Fancy that.

While you’re fancying, go order yourself some pickup or delivery.

HCI Students’ Questions: Answered (Part 2)

Sunday, December 19th, 2010

Let’s take a crack at a few more questions from HCI students. I’m going to give a real thorough answer to one question, and knock out a few more with a simplified response. If you haven’t done so already, check out part 1 of this article.

  1. What are professionals & hiring managers looking for in a designer?

    This is a topic that’s particularly near and dear to my heart at the moment. I’m in the process of hiring Interaction Designers and User Researchers at GrubHub as we speak. There are a number of things we’re looking for, including:

    • Writing Skills – Good writing is an indication of an organized mind. If you are unable to throw together some specifically tailored prose explaining why it would be great for us to work together, getting to the interview stage is a non-starter. If you’re not comfortable with your writing skills, practice! There will never be a better place to learn to write than while you’re in school. Take some classes that require lots of writing. Oh, and have someone read over your application materials before you send them in. It would be silly to get rejected from a job you really want just because you made a few typos.
    • The ability to speak in-depth about your past projects – By the time I’m talking to someone on the phone, they’ve impressed me with great application materials and personal history. The phone interview is your chance to start talking about who you are and what you’ve done. I want to know that you’ll be able to communicate with coworkers who may or may not understand what your job is all about. If you can’t explain the stuff you’ve already done, how can I expect you to explain the stuff that is yet to come?
    • Proof that you’re motivated (and excited) – Yes, the job application process is the time to go above and beyond. If you’re asked to write a paragraph, add a little visual diagram. If you’re asked to write a little code to do X and Y, throw in a little Z, just for flair. Prove why you’re going to be awesome to work with.
    • An understanding of the technology you’ll work with – No, you’re not expected to be an engineer (unless you’re applying for an engineering job), but you will be expected to communicate with engineers on a detailed level. If you’re applying for a web startup and you have never touched CSS, it’s time to start learning. Once you’re comfortable with that, teach yourself a little jQuery for good measure.
    • User-Centeredness – Not only should I be confident that you can sketch, build wireframes, do a little coding, and lay out page that doesn’t make me cringe, but I should also be confident that the users that my company caters to will be at the forefront of your mind. If you’re not asking questions about users during the interview, you’re doing something wrong. Questions about the user research methods we currently employ should be asked, as should ideas about what else we could be doing to assess and improve our users’ experience. That’s the whole job, in a nutshell.
    • And, of course, knowledge of all the methods you should have studied in school – This is not a test, but yes, the basics should be there.
  2. What did you learn at school that you use at work?

    Everything. Literally, everything I learned at school I’ve used at work at one point or another.

  3. What can students do to get the most out of the program?

    Everything. Don’t sleep too much. Get to know your peers and professors. Learn what kind of designer you are. For that matter, learn what kind of person you are.

  4. What do you wish you learned in this program?

    Sometimes I wish I learned more about how to actually implement things. In the end though, that’s something you can learn on the job or after school is out, so I don’t have many regrets in this category.

C’est tout for now. Enjoy!

HCI Students’ Questions: Answered (Part 1)

Monday, November 1st, 2010

This weekend I returned to my design roots and met a ton of Indiana University’s current HCI/d students.

A room full of designers

A room full of designers

I was pleased to be a member of the Alumni panel and was impressed by the questions that the students asked. I was so impressed, in fact, that I think many of the questions they asked are worth answering for myself and others. I’m going to try to do my best to provide some answers to these questions. I’ll do a few questions each day for the next few days. Let’s give this a shot.

  1. How you you describe HCI/design to people?

    Easy: HCI is the academic field that studies how people interact with machines in their environment. Design is about making things that fit well into peoples’ lives. So, HCI/design is all about making machines that fit well into peoples’ lives. Not necessarily an elegant explanation, but it does the trick.

    Outside of academia, people talk much less about the field of HCI, though it tends to be an impressive moniker when you bring it up. Professionally, I am more likely to talk about User Experience than I am about HCI. And I often leave out the whole concept of design when speaking with some audiences. Many people think of the term design as making things pretty, or relate design to fashion. That’s not the way I think about it, so I often avoid the topic altogether. Business stakeholders want to hear that you’re going to make systems that are easy to use and enjoyable, so as long as you can do that, you’re golden. Be aware of the words you use, and be mindful of your audiences’ interpretations.

  2. I have my masters degree (in HCI), now what?

    Now the fun begins! Consider your degree a starting point, rather than an end goal. Once you’ve earned the degree, it’s time to start thinking about your next goals. You’ll have to reassess these goals throughout your career and life, so make sure you plan on doing that early and often. Even the people you consider to have “made it” are constantly adjusting. You should too.

    Your degree in HCI should open some doors for you, but don’t expect it to work magic. You’ll still have to work hard every day to prove your worth. My dad used to say to me (warning: baseball analogy ahead), “Josh, you’re only as good as your next at bat.” I like that. It means that you’re only as good as the next opportunity that is provided. You can never rest on your past successes. Keep getting better with each project. But while you’re at it, make sure to realize that you have a long career ahead. Make sure you enjoy it.

  3. How do you personally stay up to date with design?

    This question was originally asked in the context of academic papers and journals, and I have to admit that I’m pretty out of sync when it comes to those publications. The first problem I have with them is that they’re expensive. It burns a little bit that I would have to spend $19 to read a paper I wrote. But I guess the publishers have to make money. That’s why I tend to read more books than articles. I get more bang for my buck when I’m buying a whole book, and my employers do too.

    In particular, I like to read the books published by Rosenfeld Media. They’re typically pretty dense, but aren’t so long that I can’t give them a quick read over a weekend. They’re nice summaries of a topic, and they go much deeper than many blogs. I also geek out on books by other publishers. I’d estimate that I read 5-8 industry-related books per year.

    Of course, there’s also plenty to read on the internet. These days I follow Hacker News pretty closely. There are often articles posted there that cause me to think deeply about design. I get a lot of other random articles from the people I follow on Twitter. In fact, looking at recommended articles has replaced my addiction to Google Reader.

    I also try to attend conferences, but that gets tough sometimes. Conferences are fun, but they’re costly in terms of the amount of time away from work, as well as the pure cost of attendance.

More to come soon…

The Best Feature: Fun

Thursday, April 29th, 2010

Sometimes, you just want something to feel right. On the site I help design, that often means adding a lighthearted aesthetic. Implementing this aesthetic comes down to the details. Check out the icon below, taken from Groupon, everybody’s favorite $1.35 billion website:

Taken from Groupon - Who is this?

Taken from Groupon - Who is this?

Who the heck is that woman? And why is she the face of an icon? Answer: Why not? Most people probably never question this image, but it adds a level of “interestingness” to the page. My bet is that it’s just a picture of someone who works at Groupon…or perhaps it’s Rapunzel. We may never know.

Please, Stop Sending Purposeless Emails

Thursday, March 18th, 2010

This afternoon, I received what one would think is an innocuous email:

Happy Birthday, joshe!

Happy Birthday, joshe!

However, there are so many glaring mistakes in this email, it’s hard to choose where to start. How about this, I’ll start with two simple questions:

  1. Who sent this email?
  2. Why was this email sent?

The first question is relatively hard to answer. I’m not sure I’m aware of a person or group named, “Personal Finance, Personal Budget and Budget Tool Forums – Mint.com.” So, is Mint.com sending me a birthday reminder? Is it from their forum? Is it from an internal group at Intuit (the owners of Mint.com)?

Let’s ignore the first question, and just assume the email came from Mint.com, the entire company. Now we have to deal with the second question: Why was this email sent? There is no content that I couldn’t have lived without in order to continue to have a good relationship with Mint.com. In fact, there’s a bunch of bad content in the email: First, today is not my birthday. This note came a cool 2 weeks early. Actually, this message is post-marked with a 2009 send date…so it’s 50 weeks late. Second, they called me “joshe.” That’s not even my real name. I just can’t think of a single reason I should receive this message.

So now I’m assuming the email was sent in error. And now that I’m thinking that Mint.com has made an error, I’m left to wonder what kind of other errors they could be making with my personal finance data.

Folks, my message here is simple: be careful with the emails you send out on behalf of your company. Email seems cheap, or even free, but every email you send has a cost to your users. Don’t send out birthday reminders. Don’t send value-less messages that have no calls to action. Oh, and please choose a sent-from name that makes sense to people outside your organization.

Thanks.

In Everything, Find Purpose

Friday, October 23rd, 2009

It really is as simple as that. As a software developer, business analyst, or even project manager, you will find yourself tasked with designing user interfaces no matter how hard you try to avoid it. Clients will tell you how they want it to look and act, others on your team will provide input, and at the end of the day you’ll have to come to some decisions. This process may not prove all that difficult, but I want to provide you with a handy trick I use when assessing whether a UI design decision is the right move. Ready for this? Here it is:

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.

On Winter and Payback

Sunday, December 21st, 2008

I spent nearly an hour this afternoon digging my car out from a pile of snow and slippery ice. I had done the same thing yesterday, though it was less ice and much more snow. Winter in a cold climate tests one’s will to commune. All those hours holed up indoors means that you’re not interacting with people, nature, or the world in general.

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.

Google Chrome’s Design Comic

Tuesday, September 2nd, 2008

So the big news on the internets today is Google’s new browser: Chrome. It’s only available for Windows as of today, and since I’m on a Mac I haven’t been able to play with it yet. But that’s ok, because Google hasn’t completely left me out of the loop. I have access to the comic interpretation of their engineering decisions.

Google Chrome Design Comic

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

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…

Ask “What if” Questions

Thursday, August 21st, 2008

What if we could travel 5 miles in less than 5 minutes?

What if we could watch movies in our own homes?

What if we could buy things for a whole day without using any paper money?

What if we could communicate with friends on the other side of the world without leaving the house?

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?