Loomio functional overview
This discussion is to reflect on the work I’ve been doing in this google doc (don't worry too much about the 14 pages, it's only about 2300 words).
This is the result of a functional analysis I've been doing since last week, reading through slightly more than 100 loomio discussions in the Loomio Community group, and also using some information that has been posted in the discussion about the strategic workshop.
As better explained in the document, the purpose of it is to identify users needs at a functional level, rather than at a feature level. I’ve also started to aggregate some of the info that is scattered over several Loomio conversations, trello cards and mockups (actually none of the trello cards are referenced yet, and some Loomio references are missing − feel free to help out). I haven’t bothered with yammer conversations as I think they should be turned into loomio conversations.
Please feel free to comment on the document, or to edit directly when appropriate.
Here we can have a discussion on whether or not we should try to go further into designing at the functional level, and what tools should we use to do so (atm there are 11 functions in the document, and maybe a trello board with 11 columns is too wide?). I would also find important to keep external references to mockups, loomio discussions etc in one place, and maybe trello cards are a good place for this.
I’ve also added a bunch of new features that came to my mind while reading the discussions and doing this analysis… See if you can spot them :P
Indeed, great work Nicolas. =)
Wow. Amazing piece of work Nicolas. I think it is going to be immediately useful to start thinking about specific feature ideas categorised into functional categories.