So, looking at the current MVP:
I think the things on the list are fantabulous. They're all pieces of functionality we need - they're things the current setup provides for. However, I worry that on its own, that means the first look people will get at Flow is..."talkpages, only I need to learn a different way of doing things now".
The "talk pages" bit of that is actually great, and it's something I think we should all think about when we're building things (be they Flow or...anything else). I'm really happy that Maryana has; hat-tip to you :). When we're building something, whatever we build, there's going to be some community inertia to redirect - and so our job is to build it in the order that best minimises culture shock. So, we start from the principle of "this is talkpages, but different", and
then we add in a drip-drip-drip of new functionality, and before you know it they're using flow. The alternative - presenting them with all of the contexts at once - risks having people dislike the whole because of a non-MVP part of it. So it's good to see this tack being taken.
Having said that; I worry about the "I need to learn a different way of doing things now". Minimising culture shock is great, but it's still going to be there - we're always forcing people to adapt, to some degree, and we need to give them something that makes them feel like it's an adaption worth making. Sticking with existing functionality for the MVP solves for a lot of the culture shock, but
only having existing functionality for the MVP exacerbates the remainder. So I'd like us to explore if we can fit something new and shiny in the MVP, that demonstrates why power users should like (or at least tolerate) flow.
I can think of a couple of things that would do this, and..probably not feel conceptually out of place for the wikiproject release:
*Being able to watchlist individual threads, rather than merely see changes for an entire page;