I talked about software design and seeing through the customer’s eyes for 30 minutes on Jobs-To-Be-Done Radio. In my favorite part we thoroughly debunked personas and talked about how situations, not attributes drive behavior. Hosts Bob and Chris are collaborators of Clay Christensen and they strongly influenced my thinking over the past year. It was a blast to chat on the show.
Start with our Best Hits on Design
- ⋆ Reminder: Design is still about words
- ⋆ The Typography and Layout behind the new Signal vs. Noise redesign
- ⋆ Backstage: How we use Basecamp to collect, share, and discuss inspiration
- ⋆ Backstage: Using Basecamp to build the Basecamp calendar
- ⋆ Behind the scenes: Reinventing our Default Profile Pictures
- ⋆ Behind the scenes: Highrise marketing site A/B testing part 1
- ⋆ What happens to user experience in a minimum viable product?
- ⋆ Lessons learned from implementing Highrise's custom fields feature
- ⋆ Ten design lessons from Frederick Law Olmsted, the father of American landscape architecture
- ⋆ Flashback: Every time you add something you take something away
Our Most Recent Posts on Design
I’ve been working on some video tests with the iPhone and I needed to mount it on tripod for some steadier shots. Some folks in the office had good things to say about the Glif from Studio Neat, but the only one we had lying around didn’t fit my phone and sat kinda goofy on our tripod plate. So, I did something I wouldn’t have imagined possible a few years ago. I printed a new one.Continued…
Recent versions of Google Chrome on OS X mangle native input buttons. I don’t know precisely when it started but no amount of CSS brute-force seems to correct the text alignment. Have you found a work-around? Do you know a little birdie on the Chrome team?
(Update: Paul Irish kindly responded and filed this bug on the Chromium project.)
There’s a flash flood warning for all of Chicago today. Unfortunately there’s water in my basement (like other Chicago home owners)...
The flood fixing company U.S. Waterproofing has a cool feature on their website. Look at who we’ve helped in your neighborhood. As you can see, they get around! Gives me confidence to give them a call—which I might do right now.
“For the modern audience, the fluidity of objects in Robert Lazzarini’s body of work, for example, immediately registers instead as having been run through the computer and messed around with. As a nod to this sea change in perception, Italian designer Ferruccio Laviani has created the brilliantly disorienting Good Vibrations storage unit for Fratelli Boffi.” Read the full article.
I love Fantastical but missed having a quick way to find out today’s date, a feature the native iOS calendar app provides with a special app icon that changes each day. To work around this Fantastical offers a clever hack: an option to display the current date as a badge on the app icon.
Since copywriting is interface design, you can do an awful lot of great design in a text editor. Don’t worry about where things will go, or how they will fit. Worry about explaining it clearly and then build the rest of the interface around that explanation.
In our industry, you’ll often hear people say things like “if someone can’t figure it out in 10 seconds then they’re gone.” Or “I checked out the site and I couldn’t figure out what they did so I left. Terrible design.” Or “if it takes more than a couple sentences to explain it then it’s not simple enough.” Or “too much to read!” Or “there are too many fields on this form!” Or “there are too many steps in this process.”
I’ve said some of these things in the past, so I understand the knee-jerk impulse that lead to these sorts of reactions.
However, something’s usually missing from these assessments of the situation: The actual customer’s motivation. How motivated is the customer to solve their problem? What are they here for?
If you’re just evaluating something purely on a design-principles basis, then it’s easy to be binary about it. Good, bad. Too slow, not clear enough, confusing, whatever.
But it’s lazy to evaluate things that way – and trust me, I know, I’ve been lazy about it in the past. I’ve just recently come to remember that you have to factor in motivation.
How motivated is the customer? If your motivation is to evaluate a design, how can you accurately comment on whether or not it’s good or bad unless you understand the customer’s motivation? Their motivation isn’t always to get in and get out as fast as possible.
Customers come to learn something, research something, consider something, buy something. If they are motivated, they may not mind spending five minutes reading. They want to read, they want to know. They’re OK investing their time to find something out if they really care about the answer.
For example, while a longer form – one that a designer might cringe at – might lead to fewer trial signups, it might also lead to higher-quality, more qualified leads. A longer form could weed out the people who are just poking around from the people who are really motivated to buy.
Is clearer better? Yes. Is brevity better? Not always. Is speed important? It depends. How much detail is required? Just enough? Should you make it easier for people to get better answers sooner? Yes. But that doesn’t mean every question demands a 10 second answer and that doesn’t mean every form needs to be three fields or less.
Graphic design is visual communication. Can you design a better graphic that communicates NYC “sugary beverage” law changes? (via Charles Go)
My green thumb is often challenged by the grocery store orchid. I never quite know how much water to give these things. So I was really happy to see this solution recently. The orchid comes with a cup! How much water? This much water. Nicely done.