Tiny Wins(joelcalifa.com)

over 4 years ago from Joel Califa, Senior Product Designer at GitHub

  • Brandon ZellBrandon Zell, over 4 years ago

    Love your article and the concept of Tiny Wins. Probably the biggest take away for me was that you can't rely on your users to bubble up these potential Tiny Wins. That's a great point and I appreciate you talking about how to identify Tiny Wins too. "Tiny Wins are often shortcuts." Ah! (lightbulb)

    One comment I guess I'll share: You mentioned Netflix's "Skip Intro" feature as a Tiny Win, but then later said that Tiny Wins should be low effort and take a short amount of time. Is that really true of Netflix's implementation of that feature? Just made me think that sometimes a Tiny Win might appear to be a simple small feature on the client side, even if there was a lot of effort involved. What do you think?

    5 points
    • Joel CalifaJoel Califa, over 4 years ago

      That's a great point, I have no idea what the implementation looked like (I assume lots of manual data entry but Netflix is king of ML so go figure). The reception was mindblowing, though, regardless of time spent. It's definitely worth figuring out an appropriate threshold of effort to expected impact. I'm sure "low" means something different to every org.

      2 points
      • Brandon ZellBrandon Zell, over 4 years ago

        Ah, that's true. 1. Factor in expected impact. 2. "low effort" is relative to every org. Good insight. Thanks!

        0 points