Get StartedFree for 30 days. No card required.

‘Lists’ Are Now ‘Projects’: A Slight Adjustment to Flow That Doesn’t Really Change How You’ll Use It

Mark NicholsLast Updated: January 15, 2015

We’re making a nice little change to Flow that we think is going to make it better for everyone: we’re changing ‘lists’ to ‘projects’.

Here’s why: first of all, we realized that lists is a confusing term for what is much more commonly known as a project — especially to people who are brand new to Flow. The name ‘list’ came about since what it represented was a group of tasks (i.e. a list of tasks), but at the end of the day, our definition of a list was always a project to anyone else in the world. So, this change will hopefully make Flow a little bit more accessible and recognizable to your future team.

Our thinking is a little bit bigger than that, though. We’re all about getting things done, and helping you wrangle massive projects that feel impossible. Something about the word ‘lists’ has an infinite feel: something neverending, that could have continual additions. A good project, on the other hand, has a firm beginning and end, not to mention the undertones of accountability and purpose — whereas a list is really just a list. This puts a little more emphasis on managers to create projects with a clear end goal — but that’s never a bad thing.

Lastly, this sets the stage for several very nice new features to come, the first of which is right around the corner (hint: it starts with K, and ends with anban). Follow us on Twitter to get the latest info about those features, which will be live on your screens before too long.