Why We Fail Blog

Learning from Experience Design Failures

Posts written by Victor Lombardi

  • Is HP Repeating Nokia’s Mistake?

    Posted on

    HP goes up against the iPad Pro with its $599 Chromebook x2

    The Chromebook x2 seems to have a lot of potential, but there are some big questions — and not just about whether the hardware is as good as it looks. The real open question is whether Chrome OS is cut out to work on a tablet. Google has been overhauling the operating system to work better with touchscreens for a couple years now, but it’s still very much a desktop system. (It’s based on the Chrome desktop browser and its display of desktop websites, after all.) That’s likely to limit how useful it is, especially in comparison to an iPad, which was designed for touch from the ground up.

    Wait, what? Is it 2018 or 2008? Ten years ago it was just starting to become clear that Nokia’s Symbian mobile operating system, a system designed to work with buttons that never made sense with touch screens, was going to get killed by the touchscreen-native iOS and Android. Fast forward 10 years and it looks like HP and Acer are doing the same thing by (mis)adapting Chrome. Why? And who is going to pay $600 for this? Especially when great Android tablets exist for around $500?

    Can Good IA Lead to Brand Failure?

    Posted on

    Here’s a story about a website I created several years ago that I had considered a success and now, upon reflection, see as a partial failure.

    When it comes to measuring the success of information architecture, I usually think of clearly measurable criteria, such as findability. I ask someone to find something in a website and measure if they can and how long it takes. Easy.

    But what if IA goes deeper than that?

    For several years I did pro-bono work for my kids’ preschool. It started one day when the school’s website disappeared. That’s right, it just disappeared. And it was just a few weeks before their big registration period. Apparently a non-profit that received a grant to make websites for schools had built a reasonably nice site for free. But when the grant ran out, the organization disappeared. And the hosting account and all the website files disappeared too. All the school was left with was their domain name.

    My wife heard about this and volunteered me to save the day. I was used to these sort of client-driven fire drills in the consulting world, so I was able to conduct some geurilla research, gather assets, and build a site based on a purchased template in a little over a week. Success, right?

    Months afterwards, the school scraped together about $16,000 to hire a local agency to build them another site. While my ego stung a bit, this decision made sense: they wanted more functions and a CMS which my site didn’t have. Fair enough. Unfortunately the agency-built site had several “coming soon” sections that were never filled in, used an oddball CMS that was difficult to use, and overall was hard to maintain.

    My version didn’t have these problems. I built a one-page site that was long but one could easily find everything by scrolling down. There wasn’t any superfluous content or navigation. But the biggest problem with it, and why the school replaced it, wasn’t the information architecture’s performance. It was about how the brand was projected by that single page. It didn’t look like a “real” website; it didn’t look “normal.” Normal websites have navigation along the top and maybe the side. The pages aren’t more than 2 screens long (with the exception of articles). And while the school was happy I came to the rescue and gave them something when they needed it, ultimately they didn’t want a site that projected an image that was outside their perception of convention.

    So that’s a lesson I learned: IA is also brand, and brand matters.

    Victor Lombardi is the design director at CapitalOne, and the author of Why We Fail: Real Stories and Practical Lessons from Experience Design Failures. He helped turn around a failing media business at Fox Mobile Group through the development of a new web platform and mobile apps. He walks the walk by developing his own product, Nickel, with the goal of making personal financial planning accessible to everyone. Follow him on Twitter or buy his book

    204 Startup Failure Post-Mortems

    Posted on

    If you’re starting up a new company or product, it wouldn’t hurt to scan these 204 Startup Failure Post-Mortems to learn what not to do from startups who fizzled.

    One in particular, struck me in a twisted sort of way: this postmortem of SunEdison’s backruptcy:

    SunEdison at its core is a boring construction company, that earns the trust of its institutional investors by being boring and managing risks … [but the company’s senior executives] didn’t want to be boring, they wanted to be a technology company.

    Victor Lombardi is the design director at CapitalOne, and the author of Why We Fail: Real Stories and Practical Lessons from Experience Design Failures. He helped turn around a failing media business at Fox Mobile Group through the development of a new web platform and mobile apps. He walks the walk by developing his own product, Nickel, with the goal of making personal financial planning accessible to everyone. Follow him on Twitter or buy his book

    Leading Groups to Learn From Accidents

    Posted on

    Etsy has created a guide for facilitators investigating why accidents happened there: Debriefing Facilitation Guide: Leading Groups at Etsy to Learn From Accidents (PDF)

    Notably, they jettison the old model that places blame on people who forgot to do something, and instead focus on learning how they can improve and making changes:

    Most traditional accident investigations tend to focus on discovering things around an event that never actually happened. In an attempt to prevent future accidents, there is an underlying assumption (Shorrock, 2014) for this somewhat peculiar emphasis, which is:

    Someone did not do something they should have, according to someone else.

    Through this lens, what generally surfaces in investigations are “findings” about what people did not do (pay attention, make the right decision, etc.) rather than what they actually did. Without anyone really noticing, these items get labeled as “human error” and through a seductive and convenient contortion of logic, an event that never actually happened is deemed after the fact as the “cause” of the accident. Perhaps unsurprisingly, this results in an obvious recommendation for the future:

    “Next time, do what you should.”

    Unfortunately, this approach does not result in the safer and improved future we want.

    The perspective now known as the “New View” on accidents and mistakes flips this thinking around, providing a different path to improvement and learning (Dekker, 2002). We wholeheartedly believe in this approach at Etsy. We’ve invested in operationalizing it on an organizational level (Allspaw, 2010) and have shared our perspective publicly.

    Engineering vs Evolution

    Posted on

    Tim Hartford talks about following the “God Complex” of designing with a great engineer vs taking a genetics-inspired approach of generating many random variations, testing them, and repeating the process over dozens of generations until you have something that works very well.

    It’s a difference of trying to avoid anything that looks like failure and embracing trail and error as part of the design process.

    Thanks to the UX Book Club Berlin

    Posted on

    I skyped in to the UX Book Club Berlin meet up and they had probably the best questions from any audience I’ve talked to. And the best compliment: “For an American, you did a surprisingly good job of answering all our questions.” 🙂

    How Twitter Won in the First Place

    Posted on

    Twitter suffers an irrepressable flow of negative criticism from the media and Wall Street. Today we hear that Twitter’s CEO is stepping down. As a media force of our time we all have a stake in what happens to Twitter.

    Eight days ago the investor Chris Sacca published a popular and very long recommendation called What Twitter Can Be. He gets into ideas about live events and hand curation I’m skeptical about, but I think he nails the high-level solution:

    1. Make Tweets effortless to enjoy.
    2. Make it easier for all to participate, and
    3. Make each of us on Twitter feel heard and valuable.

    In my book I wrote a case study on Twitter vs. Pownce. Pownce had more features. Pownce had better visual design. Pownce didn’t crash everyday. And yet Twitter won and Pownce closed down. Why? Twitter focused on making it easier to join, read, and tweet.

    1. Pownce restricted new accounts to keep its backend from overloading whereas Twitter let everyone in.
    2. Pownce focused on rolling out great features whereas Twitter focused on integrating with everyone else’s platform.

    In other words, Twitter was focused on growth at the expense of what we traditionally think of as good product design, resulting ultimately in a better customer experience because they provided a microblogging service with a critical mass of readers and tweeters.

    I’d love to see them double down on that original approach that made them great. Ignore all the bells and whistles that make the products cool for people in San Francisco and get radically easier to participate.

    Here’s a video where I talk about the Pownce v. Twitter case study.