A List Apart

Menu
Issue № 294

Learn what usability testing is and isn't good for; discover the five warning signs of a bad client relationship (and what to do about them).

Getting to No

by Greg Hoy38 Comments

A bad client relationship is like a bad marriage without the benefits. To avoid such relationships, or to fix the one you're in, learn the five classic signs of trouble. Recognizing the never-ending contract revisionist, the giant project team, the vanishing boss and other warning signs can help you run successful, angst-free projects.

The Myth of Usability Testing

by Robert Hoekman Jr.29 Comments

Usability evaluations are good for many things, but determining a team's priorities is not one of them. The Molich experiment proves a single usability team can't discover all or even most major problems on a site. But usability testing does have value as a shock treatment, trust builder, and part of a triangulation process. Test for the right reasons and achieve a positive outcome.

More from A List Apart

Columnists

Matt Griffin on How We Work

Being Profitable

So you own a business. It’s the best job you’ve ever had, and it will be forever—as long as the business stays viable. That means understanding when it's profitable, and when you may have to make some adjustments. Don’t worry—it doesn’t require an accounting degree and it won’t turn you into a greedy industrialist.

From the Blog

Ten CSS One-Liners to Replace Native Apps

Håkon Wium Lie is the father of CSS, the CTO of Opera, and a pioneer advocate for web standards. Earlier this year, we published his blog post, “CSS Regions Considered Harmful.” When Håkon speaks, whether we always agree or not, we listen. Today, Håkon introduces CSS Figures and argues their case.

Longform Content with Craft Matrix

Jason Santa Maria recently shared some thoughts about pacing content, and my developer brain couldn’t help but think about how I’d go about building the examples he talked about. The one fool-proof way to achieve heavily art-directed layouts like those is to write the HTML by hand. The problem is that content managers are not always developers, and the code can get complex pretty quickly. That’s why we use content management systems—to give content managers easier and more powerful control over content.