ted boren archives

Mark Hurst of Good Experience describes how the current financial crisis “could have been avoided had the people in charge followed a ‘good experience’ approach to their work: committing to simplicity (rather than gratuitously complicated products), a long-term approach (rather than short-term gains at everyone else’s expense), and an integrated view of their own role in the world (rather than a narrow view of ‘just keeping my head down, don’t ask me to think about it’).”

posted by ted on Wednesday, Oct 01, 2008

“Companies and organizations still can’t explain what they do in one paragraph.”
Jakob Nielsen on the ubiquitous but often uninformative “About Us” page.

posted by ted on Monday, Sep 29, 2008

“I’m just a Wanna-Bea.”
Todd, describing his new role in trying to take up the slack left by Bea’s imminent departure for a well-earned sabbatical. Bea, you will be missed! (For old times’ sake, here’s a list of all the great thoughts and images Bea has posted on Northtemple.)

posted by ted on Friday, Sep 26, 2008

Jared Spool has written a great article on what goes into a well-done critique . We have several design team reviews each month, plus many additional reviews with customers and stakeholders on specific projects. The points reviewed here about respect, design ownership, and tact are highly relevant to both kinds of reviews.

posted by ted on Tuesday, Sep 23, 2008

“If it ain’t broke, you’re not trying hard enough.”
Seen on a QA engineer’s whiteboard today

posted by ted on Monday, Sep 22, 2008

“They are not always in agreement, but they are always in harmony. They are not uniform in opinions, but they are united in effort. They are many, but they are one.”
Elder Dallin H. Oaks, writing of how Church leaders avoid contention conducting the affairs of the Church in The Lord’s Way. Just as relevant to designing in a team.

posted by ted on Tuesday, Sep 16, 2008

I’ve always been a fan of Google’s changing-yet-always-the-same logo. Here is today’s celebrating the first successful test run of the now completed Large Hadron Collider at CERN.

What’s your favorite Google logo?

posted by ted on Wednesday, Sep 10, 2008

Hurricane tracker from MSNBC
While browsing for examples of complex online mapping applications, I ran across this hurricane tracker. While I’m not sure I found anything I can use directly, and despite a few nitpicks (let me move the floating panes, and puh-lease put panning and zoom controls in the usual places and formats!), there is a lot of good here.

First of course is the news interest (check out Hannah, Ike, and Josephine under the “more” link). But most impressive to me is the number of variables they are able to show simultaneously, without overloading the viewer: category of storm over time, speed of storm (more distance between symbols = greater speed), wind speed, and direction. These are all visible in the static version, like you can see in this screenshot.

But to really get the feel of it, load and re-load the screen and watch the hurricane unfold. Watch it move faster and slower along its path and watch the cloud spin faster and slower. Watch the “current position” symbol get larger and smaller. Cool… and scary if you live on the Gulf Coast. (Take care everybody!)

posted by ted on Wednesday, Sep 03, 2008

case study

Designing in a Team:
Skills, Attitudes, and Success

Last week Cameron sent an e-mail to gather some ideas about how to succeed as an in-house designer. Aside from the more obvious (and individual) necessities of technical skill, graphical ability, and general smarts, how do you succeed in a team environment, where people have different ideas, biases, and approaches to meeting the team’s common goals?

In thinking about this, I focused on the following questions from Cameron:

What follows is a moderately more polished version of my response to Cameron.

“Skills” vs. “Attitudes”

When we talk about “having skills,” we are really talking about proficiency at manipulation—whether of the medium, of our tools, or of the people we work with. If someone says I have “people skills” or “soft skills,” they might mean I am a good manipulator; I can apply my “skills” in such a way to make others behave the way I want them to. This Machiavellian approach might get results… but there is no guarantee they will be the right results for the customer or end user.

So while soft skills are important, I think motivations and attitudes are even more important, at least if you are really in it for the proverbial Greater Good. Hence my focus below is as much on attitudes as on actions, or skills.

Develop humility

This attitude enters in to almost all of the other points I mention below. “What is right” is more important than “Who is right.” This perspective is core because without it, you hold on to the wrong ideas, or hold on too tightly to the right ones, without being able to see successful variations that might meet more needs, or the same needs better. Executing perfectly on the wrong idea is worse than executing “just OK” on the perfect idea.

Look for the good

By this I do not strictly mean optimism, though that is certainly helpful. Rather I mean actively searching for what is right in my co-workers and their ideas, instead of looking for what is wrong with them or their ideas, or focusing overmuch on my own ideas.

For example, find the kernel of truth or value in a co-workers “bad” idea or criticism, rather than tossing it out because the way it was communicated was not precise, or aesthetically pleasing, or 100% user-focused—or whatever. I frequently find that even when I do not fully agree, I am able to refine my understanding of problems and possibilities when I get past my knee-jerk reactions and look for the good. Every idea (including your own) has pros and cons; honestly examining alternatives not only improves your own decision-making, but also builds political capital that you may need down the road. Stakeholders can see that you are really weighing their ideas rather than shutting down the ones you don’t like. Later on, they may extend you the same courtesy, to everyone’s benefit.

I think it is also important to look for the positive motives of your co-workers, even when you think their idea or approach is wrong. This is easier to do here at the Church where I find it much easier to believe that everyone means well and wants the end product to serve real needs, more than they care about how they come out looking or some other hidden agenda. But I find this is a good approach in any situation, because when you treat people like they care about the right things, I find that many of them truly start to care about the right things. If on the other hand you assume others are motivated by self-interest or some other negative agenda, it quickly poisons team dynamics, creating a self-fulfilling prophecy where each team member assumes the worst—and sure enough, gets the worst.

Think “Synergy,” not “Compromise”

“Compromise,” implies that someone gets something they really don’t like, but are willing to put up with. I prefer to think in terms of synergy. Working together, the whole team can come to see what is rock-bottom required, vs. nice-to-have, vs. not-really-that-important. This requires aligning to the same goals; if team members don’t have the same vision, they will naturally feel that deviation from their own vision is to some degree a failure. If we work instead toward building a common vision, then priorities start to align and most conflicts smooth out with sufficient communication.

“Making a concession” should mean that the team together agrees than X is truly less important than Y, or that approach A will really meet the core need better than approach B—even if there are other (less important) advantages to approach B. There are of course times when one discipline or another has to make a decision contrary to the consensus, because they have that stewardship and have to be accountable. But if that trump card is played too often, morale goes down, team members retreat to their own domains, and silos get erected. Far better to persuade than compel (see Doctrine and Covenants 121:39-46).

Success is when the customer is happy

Customer happiness is highly correlated with whether they feel “listened to,” and that in turn has a high correlation with whether they can see their ideas filtered through your design process and manifested in the product. That doesn’t mean that the customer designs the product, but it does mean that they can see their concerns and ideas have been addressed. Good communication skills help, but you must also be able to transform what you hear into what you design.

This matters more than met timelines, executing exactly to plan, or anything else. Failing on those measures could certainly affect customer satisfaction, but it is important to me not to confuse those things with the ultimate goal, which is people happier using your product than they were before. The more happy, the better.

Wear the hat that needs wearing

Each project and team is different, even in-house. So wear the right hat for the job, and don’t get too used to your favorite one:

That’s how I see it. What do you think?

posted by ted on Thursday, Aug 28, 2008

“It’s mostly a matter of attention span…”
Bea, commenting on the difference between a business analyst and an interaction designer. Or something like that. I stopped paying attention…

posted by ted on Tuesday, Jul 22, 2008

Webslug: Helping measure the worldwide wait… sorta

Webslug claims it can “help you measure the worldwide wait.” Cool tagline, but I’m skeptical.

The time I got back on one site was infinitesimally small (less than a twentieth of a second) when personal experience shows it takes around 10 seconds. Another site showed over 40 seconds when my experience has been around 20 seconds. And finally the site doesn’t answer the question, “How fast is it at a given connection speed?” It just gives seconds to load without the context of a data rate. (The Firefox Throttle Add-On does this nicely, but only on the Windows version.)

On the upside, it does let you compare two sites to each other and collects measurements of all the sites that get tested for public review. I like these ideas, but Webslug will have to fix those deficiencies before I come back often.

One final wishlist item, the value of which was demonstrated in a presentation by Aaron Barker recently, is being able to see the difference between “page appears” (something happens to show the user that the site is loading), “page is partially functional”, and “page is fully functional” (100% loaded). If a page takes too long to appear initially, the user may get impatient and hit Refresh—which will actually delay them further by restarting the whole process. So even if it’s not fully functional there is value to getting something up there quick, even if it’s not the full meal deal. But I’m not sure an automated tool could really do that… Someone prove me wrong please!

See Webslug for yourself.

Also check Yahoo’s best practices for increasing performance on the front end. (Thanks for all your recent help on this stuff Aaron!)

posted by ted on Thursday, Jul 10, 2008

“Web analytics is a dangerous game. If you measure the wrong thing, your metrics won’t just be weak — they’ll be directly misleading and might cause you to pursue an erroneous strategy that reduces your design’s business value.”
Jakob Nielsen on why Unique Visitors Must Die

posted by ted on Monday, Jul 07, 2008

Check out the Pew Internet & American Life Project for boatloads of data about who uses the internet and how. Example reports: Home Broadband 2008, Polling in the Age of Cell Phones, and The Internet and Consumer Choice. I will be returning soon…

posted by ted on Thursday, Jul 03, 2008

“theOneAndOnlyHotSpotIndicator”
ID applied to a div on maps.live.com . Holy Semantics Gone Haywire, Batman!

posted by ted on Wednesday, Jul 02, 2008

Interesting interview of Dana Chisnell by Jared Spool on why recruiting for usability participants should not be driven by standard demographics, but instead be more focused on task familiarity, skills, and behavior. I think this applies to our design thinking too; demographics reinforce stereotypes and can obscure the real audience issues you should be focusing on.

posted by ted on Wednesday, Jul 02, 2008

“I’m not sure if there’s a cure for what ails me today. But if there is, I bet it’s downstairs and I bet it contains chocolate.”
Overheard on Marla Erwin’s Twitter feed while backtracking from Mint

posted by ted on Friday, Jun 27, 2008

Accessibility on NorthTemple

UPDATE: Since this article was first written, Jason has implemented a very useful archive for Northtemple, including everything tagged with “accessibility”.

ORIGINAL POST: We have a lot of traffic coming to North Temple to read Aaron’s Accessibility Checklist (the one he vowed he’d never write). While you’re here you might check out some older accessibility posts (still working on that archive, right Jason?):

Plus a collection of short quotes and links:

(By the way, and totally unrelated to accessibility, Microsoft’s Live search helped me find all this stuff with their site search where Google failed… What’s up with that?)

posted by ted on Friday, Jun 20, 2008

“In a small company [the attitude] is, “Hey, let’s launch it and let’s see if the users like it.” There was a time a few years ago where Yahoo had more of that mentality. But as companies get bigger and bigger, many of them reach a point where they can’t do that as quickly.”
Jeremy Zawodny of Yahoo in a Businessweek article on recent management departures

posted by ted on Friday, Jun 20, 2008

Good examples and discussion of why proximity matters.

posted by ted on Thursday, Jun 12, 2008

LDS Media Talk : Sharing Technology Ideas for LDS Parents and Youth. A new joint effort by our CIO, Joel Dehlin; the Audiovisual Department’s Managing Director, David Nielsen; and LDS.org’s product manager, Larry Richman.

posted by ted on Wednesday, Jun 11, 2008