Nils Davis
Aug 23, 2017 · 1 min read

This thinking goes all the way down, too. As I responded in a comment to John Schenk, big outcomes are enabled by sub-outcomes. To enable the big outcome “a place where I can keep up with all my friends” (Facebook), I need to enable smaller outcomes like “a way to ask my friends to connect with me” and “a way to show my friends this picture I just took of the most amazing breakfast.” Which then become features.

If I’m considering a feature for my product, and I can’t figure out what outcome it supports, that’s a big red flag. Actually, this is a bigger problem for enhancement requests from customers. You want to make sure that you understand the outcome they are hoping for (even if they don’t yet know they’re hoping for it) before you implement the solution that delivers that outcome.

)

    Nils Davis

    Written by

    Product management, green building, using language better in politics.