One lesson that comes to mind may not be from Lists per se but from that time (and is relevant to Branch): when you add in a new feature — like a whole new moving part — to a launched product you incur a cost going forward for the further development of that feature.
Basically, it's seductive to think "Oh, we'll build this new thing and it'll take a bunch of work but then we'll have it once it's launched." But really you're not just signing up to build that new piece but to maintain and improve that piece for the rest of time (or until you kill it which happens rarely). Technically, you'll need to continue to scale the feature. But product-wise, you'll need to continue to enhance and improve as you figure out how that piece fits in.
Preface: playing around with some of branch's features because I think their short annotations/convos as a product could inform noodlings/notes.
Think this quote from Jason Goldman on Twitter's features, which, depending on how you look at it, seem to simultaneously to be huge and small in number, is good to think about with us.
Thanks for your feedback! Team Branch
