Group Request Form

I've been talking to @umaholla who suggested we should ask for location information on the form. @benjaminknight and I have also talked about getting further detail about the group type (to determine whether or not they would have a formal budget). Also, for those groups that indicate a willingness to contribute, it would be good to find out what kind of contribution they have in mind.

What other information do we want to gather?

Being able to allocate the group to a Loomio community builder/ ACC manager so it is really visible on the page who has picked it up would be great. Definately email and name for contact without having to go into view,
Being able to click right through on that email address would be awesome

For the sake of being able to report on viral growth, it would be useful if when the request form is used by a logged-in person, their user id was recorded.

We're not currently asking for people's names in the request form - it's kind of a trade-off, adding an extra field but getting the benefit of knowing who to address when we write back.

It's not a huge roadblock to not have a name, but it would be nice. What do others think?

I'm indifferent. Happy to add it if you want. The form is getting quite long though.

Two weeks ago we came up with this set of mockups for the new group request process.

We need to finalise this design so we can get it implemented. Can we start by identifying the remaining pieces of work?

Here's what I can see:

1. Agree on language around the payment section of the Group Request Form @benjaminknight @vivienmaidaborn
2. Figure out what metrics we want to collect @simontegg @matthewbartlett
3. Confirm that we really do intend to process all requests within 48 hours.

p.s. Here's the words that go with the pictures:

Group requests
The process starts with a GroupAdmin requesting a new group with the Request New Group Form:

• The form is redesigned to cover 'tell us about you', 'tell us about your group', 'can you afford a subscription?', and any further survey information we might need.
• On completion, they are taken to a confirmation page and emailed a verification link.
• On verification, we tell them we’ll review the request and get back in touch within 48. We’re in grown-up territory now!
• While they are excited about their new group, we give them information about how to be a good Group Admin, and provide them a template email to send to all their prospective group members.
• The request comes into the SysAdmin panel (yesterday we were calling them LoomioAdmins)
• SysAdmin reviews the request to determine if the group is high- or low-touch, and either invites them to set up a group immediately, or defers their request for a specified length of time
• All requests are sorted depending on what actions are required.

@richarddbartlett Re. your point 2 below: I've talked with @simontegg and we think we'd just like to collect the user id (if available), and IP address (to get the city of the requestor).

@matthewbartlett how do you feel about the survey metrics we're currently gathering: group sector (community, government, business, other) and geographic distribution?

@matthewbartlett @richarddbartlett I also left a comment on the balsamiq account

@simontegg I'm having trouble finding that comment — can you post a link?

@simontegg and @neva's comments are here @matthewbartlett: https://loomio.mybalsamiq.com/projects/invitationprocess/Group%20Request%20Form

Maybe as a rule of thumb we keep all conversation on Loomio? Balsamiq does a terrible job of notifying the right people of comments.

@richarddbartlett Boringly enough, I get a Page Not Found on that link.

I believe markdown is converting the %20 to a %2520. Try this?

I'll just post my comment here:

"This is good. Metrics would like to have city/town as well as country information on new groups.

Its not a biggie but the way we've been thinking about customer classes is "subscription", "non-subscription-free" and "non-subscription-donating". This doesn't quite line up with the two categories here. It may also help to seed/allow for the idea of donating to Loomio if the second option was changed to "My group doesn't have the budget to pay for an ongoing subscription to Loomio",

I notice we are not asking for a group geographical dispersion indicator, as in the original group request. It could be useful to see how much of a factor this is with engagement

To answer @richarddbartlett 's question on the usefulness of geographic dispersion indicator (in Balsamiq).

Not too hard, but time-consuming . Now that we have a complete action log I can reverse engineer a time-series of every group's membership count using the "add_user_to_group" action ( and consequently engagement rate).

Then run a regression of engagement vs group size, group age, app age (or # of app actions available), and geographic dispersion indicator, . I think this would be useful to know, but I was going to prioritise business modelling and investment invitation this week. I believe business modelling is a dependency for some grant applications.

@simontegg, @richarddbartlett, I've added distribution_metric to the columns that get exported by the stats rake task. That's grouped with a bunch of other stats export improvements that are waiting on a chat about their privacy implications.