Archive for the ‘General’ Category

I’m Leaving AOL. Here’s What’s Next.

Wednesday, December 21st, 2011

In early 2010 I left my job as Director, User Experience for Yahoo! Messenger. After three years I was ready for something smaller, where I’d have more of an impact and spend less time fighting big company politics.

But something was brewing at AOL. It had a portfolio of embarrassingly bad products and was admitting that publicly. Tim Armstrong (AOL’s CEO) and Brad Garlinghouse (head of Consumer Applications and famous for his “Peanut Butter Manifesto” criticizing Yahoo’s lack of focus) pulled in Matte Scheinker to fix the problem. Matte — my former manager, ongoing mentor, and one of my absolute favorite people — invited me to help found his new Consumer Experience team. The opportunity was too intriguing to turn down. So I weathered the inevitable, “AOL? Really!?” from friends and family and signed on in May 2010.

Armed with authority over AOL’s product review process, the three of us — Matte, Christian Crumlish, and me — set out to turn terrible experiences into great ones. We consulted, pleaded, designed, brainstormed, fixed typos, debugged code, cleaned trash out of conference rooms. It was exhilarating. The team grew and flourished; by fall 2011 there were seven of us. In the course of it I got to lead the TechCrunch redesign, build an internal social network, and meet and earn the respect of product teams across the company.

(more…)

The Frog and the Bunny: A Parable

Thursday, November 17th, 2011

The Frog and the Bunny took a road trip to San Francisco. The Frog drove, because he’d done this before. The Bunny navigated, looking for a balance of speed and scenery.

They drove all day. They drove all night. They stopped at a Denny’s in St. Louis. As they dug into their Moons Over My Hammy the Bunny said, “Tomorrow we’ll make for Denver. It’s a flat, boring ride but then we’ll have the plains behind us and see some mountains!”

Just then a long, furry head emerged from the booth behind them. “I couldn’t help overhearing,” said the Ferret. “I’m headed to San Francisco too. May I join you?” The Bunny looked worried but the Frog said, “Sure! I can see from your trucker cap that you’ll add value to our little adventure.”

The Ferret slipped into their booth, grabbing a mouthful of Bunny’s dinner. “All this speculation about routes is silly,” he said. “Look out that window! Hundreds, thousands of cars headed off on their own adventures. Surely our best route will be the one with the most cars. Let’s count how many go each way and follow the biggest crowd.”

“That’s a great idea,” said the Frog. And they headed south. (more…)

Mossberg on Jobs: Risk-Taker, Perfectionist, Reductionist

Thursday, August 25th, 2011

Walt Mossberg on Steve Jobs:

He did it because he was willing to take big risks on new ideas, and not be satisfied with small innovations fed by market research. He also insisted on high quality and had the guts to leave out features others found essential and to kill technologies, like the floppy drive and the removable battery, he decided were no longer needed.

I’m often hard on Apple. But it’s because I can be: I hold them to a higher standard than their competition because it’s feasible to do so. Steve Jobs seems to have led Apple and often the whole industry through his uncanny gut instinct, willingness to take risks, and unerring attention to detail. We need more of that if we are to continue innovating.

Redesigning TechCrunch: We Picked this Logo Just to Piss You Off

Thursday, July 14th, 2011

I’m excited to announce the redesign and relaunch of TechCrunch.com, a popular tech news site with over 40 million visitors per month. I’ve been leading the project as product manager and design lead since January. For details check out my launch post over on TechCrunch.

AOL? Really! My First Year as an AOLer

Thursday, May 12th, 2011

Time flies. It’s been a year since I joined AOL as part of Matte Scheinker‘s Consumer Experience team. At the time my teammate and fellow ex-Yahoo Christian Crumlish wrote a post, “AOL?!? Really?” that captured the disbelief and shock among friends and relatives who heard about our new gig. And honestly, it wasn’t what I’d expected my next move would be when I decided to leave Yahoo! a few months earlier.

The AOL described to me was in the process of reinventing itself: an aging internet icon that acknowledged the need for fundamental change, that didn’t shy away from the dark corners of its product portfolio. The role was intriguing too. The Consumer Experience mission: to “ensure that AOL only builds and launches the highest-quality products.” The three of us were “ninja janitors,” cleaning up the mess of AOL. We might be accomplished designers and product strategists — but no job was beneath us. The promise: be a part of AOL’s turnaround. Develop standards and practices. Dig in with product teams in need of help and make things happen. Learn from industry veterans. Become better product managers, designers, and most of all businessmen in the process. Learn how to make change happen. (more…)

Refreshing the Website: Creating a Better, Single-Page Experience with Ajax

Saturday, April 2nd, 2011

Since the term “Ajax” burst onto the scene in 2005, it has changed the Internet. Apps became more interactive; desktop paradigms migrated to the web and evolved in the process; and the Web as a platform began to come into its own.

That change hasn’t affected the core of how a website works. Sure, modules load in asynchronously; some sites use Ajax to load in notifications; and Facebook Like buttons mysteriously appear as you scroll. The typical blog or brochure site is a page-based experience; why overcomplicate things when the Web is, at heart, a page-based medium?

But mobile apps have popularized a new level of page-based interaction. Screens animate smoothly in and out while navigation stays put, not only providing delight but preserving context and reinforcing the user’s position in the information hierarchy. Instead of jarring blankness between screens, users see loading animations.

The No-Refresh Site

Maybe it’s time we embraced this approach for the desktop Web: the no-refresh website. Even with fast load times a full page refresh disrupts context. With Ajax we can leave navigational elements in place while loading in new content. We can bring that content in via animations that reinforce how we’re moving through the information hierarchy of the site. And even with animations, such actions are liable to feel lighter-weight and thus encourage exploration — not least of all because a Back action will be so immediate.  (more…)

Comparing Mobile Web (HTML5) Frameworks: Sencha Touch, jQuery Mobile, jQTouch, Titanium

Sunday, January 23rd, 2011

It’s been an exciting year for the mobile Web. Adoption of HTML5 and CSS3, improved performance in mobile browsers, and an explosion of mobile app frameworks mean it’s more feasible than ever to create rich, interactive Web experiences for mobile devices. Using a wrapper like PhoneGap, you can distribute them via the native app stores for iPhone, iPad, and Android —targeting multiple platforms with a single codebase.

Or can you?

I needed a platform for Pints — a mobile app that answers answer the question, “Which beer should I order?” As someone who works in Web technologies on a daily basis I saw HTML5 & friends as an alluring option.

Pints isn’t complicated: a home screen, a few lists screens, a few forms. Its greatest complexity lies at the data level: as an iPhone app destined for San Francisco bars it can’t possibly rely on an Internet connection, so it has to keep a local copy of the beer database and sync it with the server when that’s available. HTML5 has the necessary building blocks in the form of several offline storage options; it’s just a question of writing the synchronization code.

Mobile Web developers have a plethora of frameworks to do the heavy lifting for them: animated transitions, toolbars, buttons, list views, even offline storage. Most of these are new and the landscape is shifting rapidly. I started Pints in jQTouch, then migrated to jQuery Mobile, and finally rewrote the whole app (now in private beta) in Sencha Touch. Along the way I also investigated Appcelerator’s Titanium Mobile. Here’s what I found: (more…)

Phone Wars: iPhone 4 First Impressions

Tuesday, July 13th, 2010

As long-time iPhone owners we’ve done our share of railing against AT&T. Time to put our money where our mouth is. We’ve ordered an iPhone 4 (with AT&T) and a Droid Incredible from Verizon. In 30 days we return one. Two phones enter…

We’ve had the new iPhone for three days now. Since there are plenty of full reviews elsewhere, I’ll restrict myself to a few highlights.

It’s fast. Fast, fast, fast. I cannot overemphasize how important this is. Presumably it’s a combination of the faster processor and the pseudo-multitasking, with an emphasis on the former. (I am upgrading from an iPhone 3G whose iOS4 upgrade slowed it to a crawl.)

The new screen is beautiful. It’s evolutionary, but the type of evolution that feels revolutionary because it makes such a difference. I was doing my Kindle reading on an iPad, but the crispness of text on the iPhone 4 has switched me back to it. In some ways it feels like a different technology.

The hardware is not as dramatically different from previous generations as Apple would have you believe, but nice, compact, clean-looking. It’s a little harder to pick up because of the square edges.

The best news is the signal. Reception is definitely better in San Francisco – and the Mission in particular. It’s possible to make calls in our apartment and to load data on the street, though it’s still spotty. Whether that’s the device or AT&T’s ongoing improvements is unclear: we know they’re adding towers, and our iPhone 2G seems to be doing a bit better as well.

Then there’s the much-discussed antenna issue. It’s real, not simply cosmetic, and confirmed by Consumer Reports. (Mini-rant: the frustrating part is not the hardware problem, but Apple’s all-too-typical response ranging from, “What problem?” to “You’re the problem.” It takes a special brand of arrogance to deny something so easy to reproduce.)

Otherwise…well, it’s an iPhone. Overall a delight to use, irritatingly locked down at times, occasionally annoying. The Droid should be arriving soon…

Trade-offs

Wednesday, June 30th, 2010

Great products require trade-off. Which features should you promote with big, glossy buttons? Which materials or technologies should you use, and at what cost? When should you release it? How heavily should you test it first? Should you fix a crash bug that affects 2% of users or a cosmetic bug that affects 90%?

These trade-offs are unavoidable. If you don’t make them explicitly, you make them implicitly. Can’t decide which feature get a big button? You can create ten buttons but you’re making another trade-off: each will be a little less prominent, and your product’s simplicity and elegance will suffer.

Trade-offs are necessary at every stage of the product lifecycle:

  • Apple is often praised for simplicity. Less is more: remove all the physical buttons and do the rest in software. But that’s not the whole truth. The iPhone has two volume buttons, a power button, a Home button, and a ringer switch. Only the power button is necessary. Someone made a trade-off, sacrificing a certain degree of simplicity for the convenience of four more buttons. The result may, in fact, feel simpler: without taking the phone out of my pocket I can adjust the volume or set it to vibrate. What we call simplicity is, in fact, a successful trade-off.
  • Facebook has repeatedly favored speed over caution, angering users by releasing features and design changes (e.g. the newsfeed) without vetting them thoroughly. Many look to the resulting uproar as a cautionary tale, but I believe this is the wrong lesson. At worst, Facebook’s tremendous growth has proceeded in spite of these choices. But I suspect Facebook has succeeded because of them: by trading speed for pre-release research and by making sure they can correct course quickly, Facebook has innovated, stayed ahead of the competition, and gotten free user research in the bargain.

Make no mistake: trade-offs are hard. They require sacrifice. They require risk. But then, it should come as no surprise that these qualities are needed for great product design as well.

A Great Compromise

Tuesday, March 2nd, 2010

A great compromise