Loomio

New group flow: an overview of design and development

Richard D. Bartlett PublicSeen by 41

Screenshots

Check out the latest screenshots here.

Flow

We had an excellent workshop this morning, taking a high-level view of the process of getting a new group setup on Loomio:

Diagram

  1. Group admin requests a new group on Loomio
  2. System admin approves request...
  3. Group admin self-selects as: A: 'My group can't afford to pay a monthly subscription', or B: 'My group can afford a subscription', and/or C: 'My group needs additional services' (engagement/facilitation consulting, support/training, etc).
  4. Then they set up the first discussion & decision, invite members in, and get stuck into using the tool.
  5. After the group has had demonstrated success with the tool...
  6. ...if the admin has selected A (e.g. if they are in an informal network without a budget), individual users in the group will be given the opportunity to 'Pay What You Can': a one-off or repeating contribution of their choosing.
  7. ...or if the admin selected B they will be billed just like any SaaS product, e.g. the way Yammer does it, with a subscription rate calculated on group size.
  8. ...or if the admin selected C they can ask for additional support, e.g. a phone call from a Loomio account manager to discuss consulting services etc, and/or an online facilitator that can collaborate with them on setting up their group.

Richard D. Bartlett

I was thinking it would be good to have the customer development (ugh can we come up with a better term) people having this flow in mind when they talk with users. Their feedback over the next couple of weeks will be critical to developing steps 7 & 8.

@alannakrause @sophiejerram

Danyl Strype

@richarddbartlett I agree that "customer developmet" is ick. What about replacing customer with 'user' or 'public', and development with 'engagement' or 'outreach'? Or what about something totally different like 'adoption facilitator'?

Sophie Jerram

I love this flow chart, well done all you fullas who developed it. WE really do need a customer engagement whatsit team.
Customer services is cheesy but it's also familiar.

Richard D. Bartlett

I've updated the context with the latest screenshots showing progress to date.

Notes:

  1. we're removing the intermediary "Yes I've talked to my group" page
  2. the language in the group request form is much more accurate and descriptive than it is currently (screenshot 2)
  3. we're using email verification to guarantee we have email deliverability (shots 3-4)
  4. sys-admins compose a unique message for each new group they approve and explicitly offer to help (shots 8-9)
  5. new group admins have to click through a tutorial before they get to the wizard (shot 11) - we're going to workshop the text in here tomorrow.
  6. the wizard will have additional help information on the right half of the screen (shots 12-14)

Next up, we'll pull together the screenshots for the new user flow, and the 'pay what you can' system. Then once that work is complete we can move on to the subscription system.

Here's that update I promised @sophiejerram :)

Matthew Bartlett

Looks really great.

Could #10 be partially populated with data from #2?

Sophie Jerram

@richarddbartlett is there any chance that the email that gets sent in #4 can include the link on #5 so that they get two chances to think about group collaboration?

This is dovetailing into the understanding about how important the design of a discussion is to the success of the group and relates very firmly to the thinking we had this week in the business team about a) what is basic ABC for getting good discussions going and b) where we can really ‘add value’ with the strategic and hi-touch customers